Added a new configuration option to enable or disable escaping special VSCode snippet variables. #16
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
added 6 commits
April 30, 2025 12:59
…ng special VSCode snippet variables.
…le to get the override to work. For now, escaping is exclusively controlled by the snippet-generator.doNotEscapeSpecialVariables configuration value.
|
Thanks for the PR, Jay! Unfortunately, I just started vacation, will get back to you in a few weeks. If the PR works for you, you can build it to a location extension to use before I incorporate these changes into the extension, thanks! |
|
Awesome! Glad it made it in the new version. Thanks for considering and approving the 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.
Hey Wenfang Du,
I updated your extension to include a configuration option to enable/disable escaping VSCode snippet variables like
$name,${name:default}, or$TM_SELECTED_TEXT.The configuration option is
doNotEscapeSpecialVariablesand can be set at a user or workspace level. It defaults totruefor all languages except PowerShell due to the fact that PowerShell variables always start with a dollar sign and snippets will become corrupted.I've outlined this in detail in this issue.
This is my attempt to remedy the problem.
It would be great if you merged this, but if not - I'll fork my own version and continue development there.
Let me know your thoughts!