add .vscodeignore syntax highlighting - #64960
Closed
Donald Pipowitch (donaldpipowitch) wants to merge 1 commit into
Closed
add .vscodeignore syntax highlighting#64960Donald Pipowitch (donaldpipowitch) wants to merge 1 commit into
Donald Pipowitch (donaldpipowitch) wants to merge 1 commit into
Conversation
Contributor
|
The correct place for this is extensions/extension-editing. I made the change. Still, thanks for the PR Donald Pipowitch (@donaldpipowitch) ! |
Contributor
Author
|
Thank you! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have no idea, if this is the correct way to do it 😄 I created a new extension called just
vscodeto handle VS Code specific features. I could imagine to have more VS Code specific functionality in the form of a built-in extension (e.g. also for things like.vscode/*files).I guess current VS Code specific features are currently included somewhere in the
src/? But I'm not sure if you want to maintain language-to-file-mappings there as well. I'm happy to move this change to a different place and to hear feedback! 😄