fix: fix escaping bug introduced by backtracking#162
Merged
Conversation
satazor
force-pushed
the
fix/escaping-windows-backtrack
branch
from
5a0c8ea to
f0a7c65
Compare
Contributor
Author
|
Build is passing on windows nodejs 18. Going to merge this since I'm pretty sure it fixes the issue. |
ghost
mentioned this pull request
|
Does this resolve this issue as well: #141? |
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
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.
There is an escaping bug introduced in #160. This pull-request fixes it.
Closes #163