fix(tagged_literals): #1717 Use tagged literals in jest tests #3902
Conversation
This file contains 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
edemaine
reviewed
Nov 12, 2023
| expect`\xrightarrow{x}_2`toBuild(); | ||
| expect`\xrightarrow{x}_2^2`toBuild(); | ||
| expect`\xrightarrow[under]{over}`toBuild(); | ||
|
|
There was a problem hiding this comment.
CI reveals that .s are missing in these examples. You can use yarn and then yarn test:jest locally to reproduce CI testing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is the previous behavior before this PR?
initial syntax :
expect("\underrightarrow{x}").toParse();
What is the new behavior after this PR?
Babel 7 supports revised template literals
hence changed syntax : expect
\underrightarrow{x}.toParse();issue number: #1717