Config for files to be treated as JSON Schema files #39
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
jdesrosiers
requested changes
May 16, 2024
jdesrosiers
reviewed
May 22, 2024
jdesrosiers
reviewed
May 22, 2024
jdesrosiers
requested changes
May 24, 2024
|
I merged these changes. I know you're still working on handling the semantic tokens issue, but I'm happy with where this is at at this point and I suspect there isn't anything we can do about the that issue anyway. If you figure something out, let's do a separate PR. |
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.
Resolves: #5
-Config for files to be treated as JSON Schema files
-Semantic tokens are built only for files watched.
-Not all files are watched at initial workspace validation but only user-defined files.
2024-05-24.22-37-07.mp4
2024-05-25.03-19-59.1.mp4