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
Setting the short: struct tag on the config element referred to by ConfigFileVariable is currently a noop. Currently the docs are unclear about this little gotcha.
And then calling go run . -c /some/file will generate no errors, since the -c flag is recognized, but its value is ignored when searching the actual config file.
I suspect this is something we can work around in lookupConfigFileFlag() (maybe just naively check flagsMap[configOpt.short]?) but it just wasn't enough of an itch for me to scratch. So I'm leaving the issue here until either I get around to it, or someone else beats me to it! 😉
Cheers
The text was updated successfully, but these errors were encountered:
Setting the
short:
struct tag on the config element referred to byConfigFileVariable
is currently a noop. Currently the docs are unclear about this little gotcha.E.g.: using something like:
And then calling
go run . -c /some/file
will generate no errors, since the-c
flag is recognized, but its value is ignored when searching the actual config file.I suspect this is something we can work around in
lookupConfigFileFlag()
(maybe just naively checkflagsMap[configOpt.short]
?) but it just wasn't enough of an itch for me to scratch. So I'm leaving the issue here until either I get around to it, or someone else beats me to it! 😉Cheers
The text was updated successfully, but these errors were encountered: