Remove ProjectSnapshotManagerDispatcher from ProjectConfigurationStateSynchronizer #10283
Conversation
This file contains 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
davidwengier
approved these changes
Apr 21, 2024
...Razor/src/Microsoft.AspNetCore.Razor.LanguageServer/ProjectConfigurationStateSynchronizer.cs
Outdated
Show resolved
Hide resolved
...Razor/src/Microsoft.AspNetCore.Razor.LanguageServer/ProjectConfigurationStateSynchronizer.cs
Outdated
Show resolved
Hide resolved
DustinCampbell
deleted the
refactor-projectconfigurationstatesyncrhonizer
branch
This was referenced Apr 24, 2024
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 change removes
ProjectSnapshotManagerDispatcherusage fromProjectConfigurationStateSynchronizerandProjectConfigurationFileChangeDetector. Ultimately, a lot of this code will go away once #10173 is the default behavior.As part of this change, I updated
ProjectConfigurationStateSynchronizerto use anAsyncBatchingWorkQueue. In my opinion, this is a huge improvement over the previous implementation.