Never escape string literals from textChanges#26971
Merged
2 commits merged intoSep 17, 2018
Merged
Conversation
sheetalkamat
reviewed
Sep 7, 2018
| } | ||
|
|
||
| function getLiteralTextOfNode(node: LiteralLikeNode): string { | ||
| function getLiteralTextOfNode(node: LiteralLikeNode, neverAsciiEscape: boolean): string { |
Member
There was a problem hiding this comment.
Can you make neverAsciiEscape Boolean | undefined so that in above change you don't need to pass || false?
Author
|
@sheetalkamat Please re-review |
sheetalkamat
approved these changes
Sep 17, 2018
This pull request was closed.
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.
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 #26967
Does not fix issue #26972