Extension config #18219
Merged
Extension config #18219
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
Contributor
|
code formatting change is unrelated: PR to fix in process: #18404 |
T-Gro
approved these changes
Mar 25, 2025
github-project-automation
bot
moved this from New
to In Progress
in F# Compiler and Tooling
abonie
approved these changes
Apr 28, 2025
Member
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
github-project-automation
bot
moved this from In Progress
to Done
in F# Compiler and Tooling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Description
A way to decide which extension will supply which feature relying on the new VS Extensibility configuration.
This now only works for diagnostics and semantic coloring.
It will probably not be the final solution but it's at least useful now for testing.