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
This is a bit of a chicken and egg problem. As you can see, configuration isn't loaded until the CLI is reset with defaults, at which point the default has already failed.
To be honest I am more and more of the opinion that default on existingfile should be disallowed.
Flags which are of type
existingfile
fail to work properly with a config file.My expectation was that this would succeed without error (
somefile
exists as set in config file). However it instead fails with an error:The error shows it isn't looking for
somefile
but for the defaultmyfile
(which does not exist).Tracing in delve shows it fails in the call to Reset before the resolver is run:
kong/kong.go
Lines 290 to 298 in 6c216a3
Removing the
default
value allows it to pass the call to reset, but is less than ideal since now it isn't possible to configure a default.This may be the same underlying issue as in:
This may be a regression since I also see #297 and #319 tried to fix variants of this before.
Looking at the debugger again I see that
Active
has been set totrue
which seems to run counter to the idea presented in PR #319.The text was updated successfully, but these errors were encountered: