-
Notifications
You must be signed in to change notification settings - Fork 4k
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
BackgroundAnalysisScope enhancements #57172
Conversation
Addresses first two parts of dotnet#57146
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Show resolved
Hide resolved
… ActiveFile background analysis scope is enabled. This is required because a top level change in ActiveFile mode would have cleared all analyzer diagnostics for non-active documents and persisted empty diagnostics state for those documents, and we need to reset that state on active document changed to ensure up-to-date analyzer diagnostics are shown for newly active document.
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Outdated
Show resolved
Hide resolved
@dotnet/roslyn-ide Ping for reviews. |
How does this surface to the user? |
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Show resolved
Hide resolved
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Show resolved
Hide resolved
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Outdated
Show resolved
Hide resolved
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Outdated
Show resolved
Hide resolved
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Outdated
Show resolved
Hide resolved
...es/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer_GetDiagnosticsForSpan.cs
Outdated
Show resolved
Hide resolved
...ures/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer_IncrementalAnalyzer.cs
Show resolved
Hide resolved
...ures/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer_IncrementalAnalyzer.cs
Show resolved
Hide resolved
...ures/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer_IncrementalAnalyzer.cs
Outdated
Show resolved
Hide resolved
src/Features/Core/Portable/SolutionCrawler/IncrementalAnalyzerBase.cs
Outdated
Show resolved
Hide resolved
Will remove Razor workarounds in immediate follow-up
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Outdated
Show resolved
Hide resolved
…ementalAnalyzer.Executor.cs Co-authored-by: CyrusNajmabadi <cyrus.najmabadi@gmail.com>
…ementalAnalyzer.Executor.cs Co-authored-by: CyrusNajmabadi <cyrus.najmabadi@gmail.com>
…ementalAnalyzer.Executor.cs Co-authored-by: CyrusNajmabadi <cyrus.najmabadi@gmail.com>
@CyrusNajmabadi @sharwell All comments should be addressed now. Thanks! |
src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.Executor.cs
Outdated
Show resolved
Hide resolved
...ures/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer_IncrementalAnalyzer.cs
Outdated
Show resolved
Hide resolved
I'm likely ok with this if Sam is ok :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm signing off. But this needs a second signoff from @sharwell :)
Closes #57146
BackgroundAnalysisScope.None
for compiler diagnostics only editing experience.BackgroundAnalysisScope.ActiveFile
so we execute compiler analyzer for all open files and remaining analyzers for the active file.BackgroundAnalysisScope.ActiveFile
to be the default scope. We will turn this experiment on for Roslyn team to enable dogfooding the experience with the new mode.[Still under discussion] A separate follow-up PR will add an experiment to switchBackgroundAnalysisScope.ActiveFile
to be the default scope.