Repository navigation
fix option name - #3624
fix option name#3624
Conversation
| `-v|--verbose` | ||
| `-v|--verbosity` | ||
|
|
||
| Enables verbose output. |
There was a problem hiding this comment.
This should specify the options for verbosity, which I think are: q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]
BillWagner
left a comment
There was a problem hiding this comment.
I ran through the commands here, and this LTGM.
@mairaw you can
when ready
|
Sorry for the delay here. I made the suggested changes but I'm still not sure whether it's the right thing to list this as a common option or if we should simply remove this option from this page since it doesn't work with every command. Thoughts @dsplaisted? |
|
@KathleenDollard should we mention that verbose doesn't work for all commands or remove it from this topic (and perhaps from dotnet -h too)? It's listed as a common option but it doesn't for all commands, so it's causing customer confusion. |
|
Can we just mark it with a note? It clarifies that it should always be just like this if it exists, but it doesn't always exist. |
|
Sure, I'll add that @KathleenDollard. |
|
@dsplaisted I decided to run some final tests before merging this. it seems that although dotnet --help for 1.x versions lists the option name as --verbose, all the commands never accepted that and in fact just dotnet --help was displaying the wrong information for 1.x. Can you confirm? /cc @KathleenDollard |
|
@mairaw I believe the help text was incorrect for 1.x, and we fixed it in 2.0. See https://github.com/dotnet/cli/issues/5502 and dotnet/cli#6690 |
|
Thanks @dsplaisted. So merged this with my last fix. |
LiveFyre comment for topic https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet:
"The --verbose option is pretty confusing.
First, the .NET Core SDK 2.0.2 reports the option as named --verbosity (not --verbose) and it requires a value from a set composed by q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].
Then, I tried every possible combination but I still can't understand how they're supposed to work. None of these commands succeeded (tried with dotnet new console).
dotnet new console -v
dotnet new console -v d
dotnet new console -vd
dotnet new console -v=d
dotnet new console --verbose
Please improve the documentation."
@dsplaisted @livarcocc does dotnet new support the verbosity flag? This is still listed as a common option when we do
dotnet --hbut it doesn't seem to work for all commands.Internal Review URL