-
Notifications
You must be signed in to change notification settings - Fork 229
Client settings tweaks, and implement VS Code configuration monitoring #11800
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
src/Razor/src/Microsoft.VisualStudioCode.RazorExtension/Services/ClientSettingsManager.cs
Show resolved
Hide resolved
...src/Microsoft.VisualStudioCode.RazorExtension/Endpoints/CohostConfigurationChangedService.cs
Outdated
Show resolved
Hide resolved
src/Razor/src/Microsoft.AspNetCore.Razor.LanguageServer/Hosting/ClaspLoggingBridge.cs
Show resolved
Hide resolved
…#78364) Since Roslyn uses dynamic registration for configuration change requests, Razor can't. Even if we could, as a document-less request, it couldn't be routed to us anyway. So this exposes a hook for us through our EA. Razor side is at dotnet/razor#11800 Part of dotnet/razor#11759
|
Oh what fun, this builds on my machine but not CI, and apparently there are no merges from upstream/main for me to do 🤦♂️ |
|
|
Thank you! fortunately was easy enough to fix based on CI errors anyway. I wonder if that indicates a project authoring issue on our end or something? Probably best not the think about it :) |
Part of #11759
This cleans up
IClientSettingsManagerand puts it back to its previous state, removingIClientSettingsReaderat the same time, and also implements a hook for VS Code to get notified when the VS Code configuration changes, and to read the settings as appropriate.Needs a bump to dotnet/roslyn#78364 before it will build