Merging main to v3 dev main #1437
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds what I think needs to be done to support categories for flags but we will see if that works. It also forces the scripts to use python2 since they blow up under python3 which is becoming the default python on many linux systems. Small fix to app_test as well so it conforms to the new Flag interface.
Let us use this repo via replace locally.
The new option `app.Suggest` enables command and flag suggestions via the jaro-winkler distance algorithm. Flags are scoped to their appropriate commands whereas command suggestions are scoped to the current command level. Signed-off-by: Sascha Grunert <sgrunert@suse.com>
If you allow a flag to be set from environment variables or files and a parse error occurs from one of them, it is very useful for the error message to mention where the value came from. Without this, it can be difficult to notice an error caused by an unexpected environment variable being set. Implements #1167.
move bool to the end of the return arguments remove "from " prefix in the source/fromWhere description remove TODO notes from functions that don't currently perform error checking
Signed-off-by: jolheiser <john.olheiser@gmail.com>
Completion file shouldn't be sourced. It should provide only completion code (source of _command) for command. It's task for package manager or user to put under $fpath.
There is no need to define custom shell var, when Zsh can be detected by checking SHELL env var.
…ynb/cli into mostynb-report_source_of_parse_errors
Update dependencies and go.mod spec
show only subcommand flags with bash completion (#1186)
Remove reflect calls for doc generation (#1259)
Signed-off-by: Jesse Szwedko <jesse@szwedko.me>
Upgrade gopkg.in/yaml to v3
Update dependencies to latest
Remove temporary go mod workaround
includes:
- running each example through `goimports`
- wrapping text at ~80 cols
- consistently using `&cli.App{...}`
- consistently using code example gates
- removing trailing blankspace
See issue #1307 for context.
subcommand names of a default command (should it be set)
Clean up the v2 manual a bit
Fix list formatting in v2 manual
feature: add DefaultCommand field to App
accept timezone for timestamps
Approve v2 addition of App.DefaultCommand @jalavosus FYI I'm merging this now with the intent to tag and push `v2.11.0`, and I'm happy to see further documentation improvements released later.
Merging main to v3 dev main
…ev-main Revert "Merging main to v3 dev main"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Get
v3-dev-mainup to date withmainWhich issue(s) this PR fixes:
N/A 😬
(what I meant to do in #1435)
(shame on me for attempting to Do Things before Being Awake)