fix(sdks): update for VSCode 1.68 #4485
Merged
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
merceyz
force-pushed
the
merceyz/fix/sdk-vscode-1-68
branch
from
c0f2871 to
e221ad7
Compare
arcanis
approved these changes
Jun 10, 2022
1 task
merceyz
added a commit
that referenced
this pull request
Oct 21, 2023
(cherry picked from commit beefef7)
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.
What's the problem this PR addresses?
VSCode 1.68 changed the format for in-memory file paths in microsoft/vscode#148940 and microsoft/vscode#149125.
VSCode 1.68 isn't released yet so this is only noticeable in VSCode Insiders and since the version detection doesn't work with the Remote Development extensions I'll leave this as a draft until it has been released.How did you fix it?
Updated the paths to match the new format.
Checklist