[fix] replace broken escaping with a working version - #3798
Merged
Conversation
🦋 Changeset detectedLatest commit: 8d07e80 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
5 tasks
Rich-Harris
reviewed
Feb 9, 2022
benmccann
force-pushed
the
fix-escaping
branch
from
February 9, 2022 19:05
0c1adae to
2495005
Compare
|
✔️ Deploy Preview for kit-demo canceled. 🔨 Explore the source changes: 8d07e80 🔍 Inspect the deploy log: https://app.netlify.com/sites/kit-demo/deploys/6204115af804370008389ffa |
Rich-Harris
approved these changes
Feb 9, 2022
5 tasks
5 tasks
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.
Cleaned up version of #3797