fix(v1): fix JSX highlighting by passing language to Prism #2196
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
yangshun
changed the title
|
Deploy preview for docusaurus-2 ready! Built with commit 2532f61 |
|
Deploy preview for docusaurus-2 ready! Built with commit 62b913c |
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.
The JSX highlighting is subtly broken:
Notice how plain text in JSX gets incorrectly highlighted.
This was fixed in PrismJS/prism#1357 but I couldn't get the fix to work at all. Then I noticed we're not passing the documented third argument to Prism, so it doesn't actually use the JSX language for tokenization.
This PR fixes it.