Handle multiline jsx strings correctly, emit escapes in jsx attributes correctly#20309
Merged
weswigham merged 1 commit intoNov 30, 2017
Merged
Conversation
mhegazy
approved these changes
Nov 30, 2017
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.
Fixes #13328
I also changed
jsxInvalidEsprimaTestSuite.tsxto actually start a new parser context for each invalid line, since this change caused a change in the error cascade in that file that I'd rather avoid. Unfortunately, that exposed another bug: we parse<a>}</a>;and<a>></a>;as valid jsx, when they should be invalid (}and>are both explicitly not part of the JsxText character set in the spec).