dotnet/roslyn

Output /p:ReportAnalyzer=true under normal verbosity

Open

#55,604 opened on Aug 13, 2021

View on GitHub
 (12 comments) (8 reactions) (0 assignees)C# (4,257 forks)batch import
Area-CompilersFeature Requesthelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Hello,

We're using /p:ReportAnalyzer=true a lot when working with analyzer performance and the output is very useful.

Downside of this property is that it works only with -verbosity:detailed that also outputs many MsBuild and target steps that we don't need. It's polluting our logs with unneeded stuff and makes the results hard to find.

Can you please update /p:ReportAnalyzer=true to output the results to the console under -verbosity:normal?

If we explicitly asks for this parameter, we'd like to have it under normal conditions.

Contributor guide

Research direction
Find where the verbosity level condition is applied for the /p:ReportAnalyzer=true output, and modify it to also output under normal verbosity instead of only detailed.
Tech stack
csharp
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
csharp
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65