-
Notifications
You must be signed in to change notification settings - Fork 726
Enable full solution background analysis #5868
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
Conversation
- Adds 2 new background analysis scope options: one for compiler diagnostics and one for analyzer diagnostics - Both the options allow the same set of values as in VS: Open documents, Entire solution, Current document and None (disabled). Currently, `Current document` option is not yet supported in LSP as we do not have a way to know which is the current active document in LSP server. - Builds on top of dotnet/roslyn#68799 - Needs couple more Roslyn side changes as a follow-up: dotnet/roslyn#68797 and dotnet/roslyn#68798
package.json
Outdated
| "activeFile", | ||
| "openFiles", | ||
| "fullSolution", | ||
| "none" |
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.
package.json
Outdated
| "Current document (not yet supported)", | ||
| "Open documents", | ||
| "Entire solution", | ||
| "None" | ||
| ], | ||
| "description": "Run background code analysis for:", |
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.
Descriptions match VS side descriptions in Tools Options dialog
|
I agree that we should not talk about solution crawling. |
d439e77 to
d36fcd0
Compare
This has now been fixed. |
|
@Cosifne if this merges without the server side change to enable the option, will that cause errors? |
Good point. Here is the server version that needs to be taken in - 4.7.0-3.23328.2. |
If client change goes in before server change. If server change goes in before client change. |
|
@mavasani since it looks like the main roslyn side PRs are merged, would you mind updating the roslyn version as well in the PR, so that it all works end to end? Instructions here - https://github.com/dotnet/vscode-csharp/blob/main/CONTRIBUTING.md#updating-the-roslyn-server-version (let me know if they're good instructions) No worries if not, Shen mentioned nothing should break if the roslyn version isn't updated, and I can update later this week |
Thanks Dave. I tried those steps but |
| "enumDescriptions": [ | ||
| "Open documents", | ||
| "Entire solution", | ||
| "None" |
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.
would have loved the descriptions and the enum member names to match :)
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.
These match the enum field names and user facing descriptions in VS. I think it would be reasonable to change the enum field names in Roslyn, and once the new values flow into this repo, we can rename the field names here as well. However, these are just internal implementation details, so not sure if it critical to make these changes.
Closes dotnet/roslyn#68553
Current documentoption is not yet supported in LSP as we do not have a way to know which is the current active document in LSP server.LSP pull diagnostic handlers should handle None/Disabled option value for compiler and analyzer background analysis options roslyn#68798