fix: preserve backslashes in template literal text (issue #462)#623
Merged
Conversation
Backslashes in template literal text are no longer treated as escape
sequences unless they appear as \\ immediately before a {{ expression.
The pattern \\{{ still collapses to a single literal backslash followed
by the evaluated expression (per Handlebars.js spec), but \\ elsewhere
in template text passes through verbatim.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #462
Backslashes in template literal text are no longer treated as escape sequences and pass through verbatim.
The pattern
\\{{expr}}still collapses to a single literal backslash followed by the evaluated expression (per Handlebars.js spec), but\\elsewhere in template text now passes through unchanged.