Skip to content
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

Simplify the code for getting source generator diagnostics into the diagnostics service. #77898

Merged
merged 5 commits into from
Mar 31, 2025

Conversation

CyrusNajmabadi
Copy link
Member

No description provided.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Mar 28, 2025
@CyrusNajmabadi CyrusNajmabadi requested a review from dibarbet March 28, 2025 20:41
@CyrusNajmabadi CyrusNajmabadi marked this pull request as ready for review March 28, 2025 21:55
@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner March 28, 2025 21:55
@CyrusNajmabadi CyrusNajmabadi changed the title WIP: Simplify the code for getting source generator diagnostics into the diagnostics service. Simplify the code for getting source generator diagnostics into the diagnostics service. Mar 28, 2025
@CyrusNajmabadi
Copy link
Member Author

@dibarbet ptal.

Comment on lines 141 to +142

result = await UpdateWithGeneratorFailuresAsync(result).ConfigureAwait(false);
// result = await UpdateWithGeneratorFailuresAsync(result).ConfigureAwait(false);
Copy link
Member

Choose a reason for hiding this comment

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

delete?

Copy link
Member Author

Choose a reason for hiding this comment

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

will do in update.

// based on 'shouldIncludeDiagnostic' predicate. More specifically, TS has special document
// analyzer which report 0 supported diagnostics, but we always want to execute it.
// Special case DocumentDiagnosticAnalyzer to never skip these document analyzers based on
// 'shouldIncludeDiagnostic' predicate. More specifically, TS has special document analyzer which report
Copy link
Member

Choose a reason for hiding this comment

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

TS has special document analyzer which report
// 0 supported diagnostics, but we always want to execute it.

is this still true, or has it moved off of roslyn?

Copy link
Member Author

Choose a reason for hiding this comment

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

literally in the process of moving them off :) PR should go in this week.s

@CyrusNajmabadi CyrusNajmabadi merged commit 5f0a49d into dotnet:release/dev17.15 Mar 31, 2025
25 checks passed
@CyrusNajmabadi CyrusNajmabadi deleted the generatedDiags branch March 31, 2025 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead VSCode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants