Skip to content

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

davidwengier
Copy link
Member

@davidwengier davidwengier commented Apr 29, 2025

Part of #11759

This cleans up IClientSettingsManager and puts it back to its previous state, removing IClientSettingsReader at 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

davidwengier added a commit to dotnet/roslyn that referenced this pull request Apr 30, 2025
…#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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants