-
Notifications
You must be signed in to change notification settings - Fork 252
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression (expansion) in dotnet restore --quiet
output
#2069
Comments
@dougbu can you share the before compared to the after and what is the expected output? |
I don't have the before picture because I closed that PowerShell window, sorry. For comparison,
And
|
Even Regardless, |
@joelverhagen please take a quick look, if this is a low hanging fruit we might take it for 3.4 release. Otherwise it will go on the backlog to be prioritized with everything else open. |
We need to decide on the desired functionality here. The previous ask was to a) have HTTP statuses (e.g. those To summarize, it seems some problems with the current implementation (@dougbu, please add to this if I am missing something):
To remedy this, I could map The only gap is to decide whether the |
Lets remove --quiet completely and add the minimal to the help. |
Fixed with NuGet/NuGet.Client#263. Spoke with @dougbu offline about this.
|
Something has recently regressed w.r.t.
--quiet
support. With the current .NET CLI, our builds look like:The text was updated successfully, but these errors were encountered: