Skip to content

Fix for issue 46942. VSIX suppressors do not run when Nuget analyzers / suppressors are installed.#47486

Merged
mavasani merged 6 commits intodotnet:masterfrom
nschuessler:nschuessler/issue46942
Sep 10, 2020
Merged

Fix for issue 46942. VSIX suppressors do not run when Nuget analyzers / suppressors are installed.#47486
mavasani merged 6 commits intodotnet:masterfrom
nschuessler:nschuessler/issue46942

Conversation

@nschuessler
Copy link
Contributor

@nschuessler nschuessler commented Sep 5, 2020

The fix is to explicitly handle suppressors on the host and analyzer side, and allow them when they suppress a diagnostic not handled on the nuget installed side.

Mention @sharwell @mavasani @kykwo

Fixes issue 46942

Hoping to get this in 16.8 preview +

@nschuessler nschuessler requested a review from a team as a code owner September 5, 2020 10:27
@jinujoseph jinujoseph added Area-Analyzers Community The pull request was submitted by a contributor who is not a Microsoft employee. labels Sep 7, 2020
Copy link
Contributor

@mavasani mavasani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks pretty good to me. Lets simplify further to only execute host suppressors if they have no overlap with any nuget suppressor/analyzer IDs.

@nschuessler
Copy link
Contributor Author

nschuessler commented Sep 9, 2020

@mavasani I'm not sure what is causing the CI failures above, it doesn't look like me unless my changes somehow affect integration testing. I have merged from dotnet/roslyn/master and am trying again.
The build+test pass locally before and after merge.

@mavasani
Copy link
Contributor

mavasani commented Sep 9, 2020

Tagging @dotnet/roslyn-compiler for test-only changes to DiagnosticDescription type.

Copy link
Contributor

@cston cston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DiagnosticDescription changes LGTM.

Copy link
Contributor

@mavasani mavasani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nschuessler!

@ghost
Copy link

ghost commented Sep 9, 2020

Hello @mavasani!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@mavasani mavasani added this to the 16.8.P4 milestone Sep 9, 2020
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

@ghost ghost removed the auto-merge label Sep 9, 2020
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

@nschuessler nschuessler requested a review from a team as a code owner September 9, 2020 22:53
@ghost ghost removed the auto-merge label Sep 9, 2020
@mavasani mavasani merged commit 3183fa2 into dotnet:master Sep 10, 2020
@ghost ghost modified the milestones: 16.8.P4, Next Sep 10, 2020
@dibarbet dibarbet modified the milestones: Next, 16.8.P4 Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Analyzers Community The pull request was submitted by a contributor who is not a Microsoft employee.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants