-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alternate input sources YAML doesn't work when flag includes alternate name #711
Comments
Thanks for the detailed bug report @wcwynn ! It does look like there are a few places where |
FYI: this also affects TOML. |
@wcwynn PR #791 can fix this bug. @jszwedko @meatballhat please review this commits |
Also mentioned this in #791, this doesn't seem to fix problems with |
Hiya! There's a known issue with the current implementation of the CLI, where altsrc is generally clunky and poorly documented. My current idea is that I'm going to move all of the |
Alternate names are described here: https://github.com/urfave/cli#alternate-names
Support for YAML is described here: https://github.com/urfave/cli#values-from-alternate-input-sources-yaml-toml-and-others
When any alternate source flag includes an alternate name, the alternate source input doesn't function as it should (i.e. it doesn't use the alternate input source data).
Code to reproduce:
Test file contents:
Output:
Have not had a chance to debug this as of yet, but documenting it for now in case others encounter this problem.
The text was updated successfully, but these errors were encountered: