fix: update global schema #5653
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
|
Download the artifacts for this pull request:
See Testing a PR |
jonaseberle
approved these changes
Dec 20, 2023
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.
The Issue
While editing the global config file, VScode reported 3 invalid keys.
Strangely, after a couple of minutes, the warning disappeared. However, the same 3 keys reported invalid again after a system restart.
The apostrophes also displayed a warning in VSCode:
"The character U+2019 "’" could be confused with the ASCII character U+0060 "`", which is more common in source code."
How This PR Solves The Issue
This PR
Manual Testing Instructions
Automated Testing Overview
Related Issue Link(s)
Release/Deployment Notes
I understand apostrophes vs. single quotes is a personal preference.
My intention is to remove warnings displayed when using the following setting:
"editor.unicodeHighlight.ambiguousCharacters": true,. We can revert that commit, as required.