- Notifications
You must be signed in to change notification settings - Fork927
fix: remove deprecation warnings when option unset#6532
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes fromall commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -257,6 +257,10 @@ flags, and YAML configuration. The precedence is as follows: | ||
continue | ||
} | ||
if opt.Value.String() == opt.Default { | ||
continue | ||
} | ||
Comment on lines +260 to +262 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Could you add a field to bigcli types similar to what cobra had for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Yeah, I'm still working through the migration. I think it'd be cool to have a value source for each field, so we can show people on the deployment page how everything is being set. | ||
warnStr := opt.Name + " is deprecated, please use " | ||
for i, use := range opt.UseInstead { | ||
warnStr += use.Name + " " | ||