Skip to content
This repository was archived by the owner on Apr 20, 2023. It is now read-only.

Changing verbose to verbosity in the help options - #6690

Merged
livarcocc merged 1 commit into
dotnet:release/2.0.0from
livarcocc:fix_verbosity_option_in_help
May 30, 2017
Merged

livarcocc merged 1 commit into
dotnet:release/2.0.0from
livarcocc:fix_verbosity_option_in_help

Conversation

@livarcocc

Copy link
Copy Markdown

…tually use.

Customer scenario

Changing verbose to verbosity in the help options to match what we actually use. Without this, after typing dotnet --help a user may see verbose as the way to indicate verbosity to our commands, but in fact, that is not used anymore and the new way to do that is --verbosity. This is misleading and confusing to our users.

Bugs this fixes

Fixes https://github.com/dotnet/cli/issues/5502

Workarounds, if any

N/A

Risk

N/A

Performance impact

N/A

Root cause analysis

The big help text is not composed by the parser, but hand crafted. We have plans to add that to the parser, but not yet.

How was the bug found?

Report by team member.

@dotnet/dotnet-cli

@MattGertz for approval.

@livarcocc

Copy link
Copy Markdown
Author

@dotnet-bot Test OSX10.12 x64 Release Build

@ghost
ghost self-requested a review May 25, 2017 20:35

{LocalizableStrings.CommonOptions}:
-v|--verbose {LocalizableStrings.VerboseDefinition}
-v|--verbosity {LocalizableStrings.VerboseDefinition}

This comment was marked as spam.

This comment was marked as spam.

@livarcocc
livarcocc force-pushed the fix_verbosity_option_in_help branch from 7fcb724 to c27b89d Compare May 30, 2017 20:05
@livarcocc
livarcocc merged commit 6db5ff4 into dotnet:release/2.0.0 May 30, 2017
@livarcocc
livarcocc deleted the fix_verbosity_option_in_help branch May 30, 2017 21:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants