-
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
Context.IsSet not working with values set from environment variables #294
Comments
Indeed, this appears to be true, thanks for raising the issue @varun06 ! |
@jszwedko I just encountered this bug too. Any update on this ? |
@AaronO unfortunately I haven't had the time to address this yet, but PRs are welcome! |
Also just come across this, I'm a Go newb so my PR wouldn't look good. |
tl;dr - this is not straightforward, and a proper solution may require reimplementing a lot of stuff My first adventures with this have me hitting some unpleasantness. A travelogue, all prefixed with a strong AFAICT :
I started down the path of building a name ➡️ |
Thanks for looking into it. |
This still/again appears to be broken,
Using urfave/cli e485446 (v2). |
@henrikhodne aha, yep, this wasn't ported correctly when I merged these changes into the |
Command `eli create -f somefile.yml`, returned error that must define either --file or --image. This because the clicontext.IsSet() were returning false if using shorthand aliases. There is fix coming in urfave/cli v2.0: urfave/cli#294 But actually we don't need to use that in our use cases so removed the extra IsSet checks.
Command `eli create -f somefile.yml`, returned error that must define either --file or --image. This because the clicontext.IsSet() were returning false if using shorthand aliases. There is fix coming in urfave/cli v2.0: urfave/cli#294 But actually we don't need to use that in our use cases so removed the extra IsSet checks.
I used IsSet() to check for some values. It works the string flag is passed from command line but not when the flag values are set with environment values.
The text was updated successfully, but these errors were encountered: