Keep automatic schema detection for more specific extensions out of user settings - #1277
Merged
Merged
Conversation
…ser settings Signed-off-by: Morgan Chang <shin19991207@gmail.com>
shin19991207
changed the title
Signed-off-by: Morgan Chang <shin19991207@gmail.com>
datho7561
approved these changes
Jul 30, 2026
datho7561
left a comment
datho7561
left a comment
Contributor
There was a problem hiding this comment.
Looks good and works well from my testing. Thanks, Morgan!
I also ran into the macOS testing bug in vscode-xml. Thanks for addressing it here!
4 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What does this PR do?
Previously, if another enabled extension provides more specific YAML support, file patterns associated with the extension were written directly to the user's
yaml.disableSchemaDetectionsetting.This PR keeps the automatic schema detection internal.
Also, updates
@vscode/test-electronto fix macOS VSCode build issue (requires Node >= 22).What issues does this PR fix or reference?
Fixes #1271
Is it tested? How?