[201911] Explicitly specify command names with underscores (continued) #868
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
|
Retest this please |
2 similar comments
|
Retest this please |
|
Retest this please |
lguohan
approved these changes
Apr 8, 2020
stepanblyschak
pushed a commit
to stepanblyschak/sonic-utilities
that referenced
this pull request
Apr 28, 2022
[201911] Explicitly specify command names with underscores (continued) (sonic-net#868) [fwutil]: Update Command-Reference.md. (sonic-net#876)
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.
Backport of #852 to the 201911 branch
Starting with Click 7.0, the default behavior of a command with underscores will be to replace with dashes.
This is to address the above default behavior change, so that the commands remain the same, extending the work done in #846 to all Click-based SONiC command line utilities.
Resolves #847
More details can be found here: pallets/click#1123
For new subcommands which haven't been included in a release branch yet, use hyphens, as this will be the direction we move in the future. I have also opened an issue to track the eventual transition: #853