Fix handling of HTML entities in JSX parsing #56
Merged
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
htmlparser2 generates separate text nodes when parsing entities. To get the numbering correct for i18next we need to merge those in our AST tree.
|
Thank you. I will publish a new version by tomorrow. |
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.
htmlparser2 generates separate text nodes when parsing entities. To get the numbering correct for i18next we need to merge those in our AST tree.
Before this change
Don't do this <strong>Dave</strong>was converted toDon't do this <3>Dave</3>instead ofDon't do this <1>Dave</1>.