Repository navigation
Move away from deprecated language configuration settings - #229
Merged
Merged
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
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.
In the July release of VSCode we added new properties to the language configuration files so that the deprecated __characterPairSupport and __electricCharacterSupport APIs in vscode.d.ts are no longer necessary.
See microsoft/vscode#9281.
I've added the new bracket pairs already to the powershell language definition in the built-in powershell extension (see microsoft/vscode@fd674fa
). You can keep your current state a while if you want to be backward compatible to pre-July versions.
This change is