Restore some parts of the progression api some legacy components (like codemap) use. #78836
Conversation
This file contains hidden or 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
src/VisualStudio/Core/Def/Progression/IProgressionLanguageService.cs
Outdated
Show resolved
Hide resolved
jasonmalinowski
approved these changes
Jun 5, 2025
3 tasks
This was referenced Jun 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Importantly, these are not the APIs that plug into Solution Explorer. This is basically just an api to take the Roslyn symbol model and return them as 'progression graph node' (similar to code model) that otehr tools then peek into for finding things like names and whatnot.
We really want to get those components off of this. But that's not happening just yet. So for now, preserve this code.