You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
..i need to name my flag "infrastructure.logger.level" without exceptions.
But what if I don't need it? For my cli interface I want its name to be "--log-level", because I don't need any nested things there.
So, I want to be able name flags as I want and configure paths as I want too, separately.
Heya! We are planning on completely rewriting altsrc for v3, so its unlikely that a maintainer will get to this issue! I'm marking it as help wanted for any other contributor that wants to help, though 🙏
Ah, I just re-read the issue. It looks like this is a feature request? Since altsrc is about to be rewritten, we aren't currently accepting feature requests for it.
This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else.
What problem does this solve?
For now altsrc requires to name my flags using dots to find them into multi-level config files.
I.e. to find a flag "level" in the following config:
..i need to name my flag "infrastructure.logger.level" without exceptions.
But what if I don't need it? For my cli interface I want its name to be "--log-level", because I don't need any nested things there.
So, I want to be able name flags as I want and configure paths as I want too, separately.
Solution description
Something like:
Describe alternatives you've considered
Using aliases is not an option there because this ugly long "infrastructure.logger.level" name will be displayed at help screen anyway.
The text was updated successfully, but these errors were encountered: