Cleanup global usings in Analyzers#4849
Merged
thomhurst merged 2 commits intothomhurst:mainfrom Feb 18, 2026
Merged
Conversation
Report diagnostic at the using directive's location instead of the entire CompilationUnitSyntax, consistent with BaseMigrationAnalyzer. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
7525115 to
49a2112
Compare
Owner
|
Thanks 😁 |
This was referenced Feb 18, 2026
This was referenced Feb 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds support for detecting and removing global using directives for test frameworks (NUnit, MSTest, and xUnit) in both the analyzers and their tests. The analyzers now flag global usings like
global using Xunit;as migration issues, and the code fixers can remove them.