Default Loaders and Config Files

Hello! 👋 I've been exploring typed-settings and the click_options decorator as instructed in CLIs with Click. The documentation is great and the library is very useful.

I had a quick question regarding the "default loaders" functionality. When using click_options(Settings, "myapp"), it appears to leverage default_loaders, which is great. However, I noticed it doesn't seem to automatically attempt to load any config files from standard locations (like in ~/.config/myapp/ or similar). Based on a quick glance at other parts of the documentation, the same seems to apply to argparse CLIs, too.

Is this the intended behavior? I was just curious because the documentation mentions "default loaders," and I was initially wondering if it might include a default behavior of checking for common config file locations. Perhaps other users new to typed-settings might have a similar initial expectation? 🤔

When you just pass an application name to click_options() >(as in the examples above), it uses default_loaders() to get the default loaders and default_converter() to get the default converter.

It could be helpful to clarify in the documentation that default_loaders in click_options, in its default configuration, doesn't automatically load files from default paths. Perhaps a note explaining that users need to use the *_SETTINGS environment variable for file loading would be useful?

Alternatively, and just as a thought, would it potentially be valuable to explore whether default_loaders could optionally include a feature to check some common locations for config files by default? Just an idea!

No strong opinions at all, I was mainly just checking to understand the current design intent and see if there are any thoughts on documentation or potential enhancements. Happy to contribute to documentation updates or anything else that might be helpful. Thanks for the library! ✨