Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entity encoding is not recognized by the lexer #530

Closed
myl7 opened this issue Mar 21, 2022 · 2 comments
Closed

Entity encoding is not recognized by the lexer #530

myl7 opened this issue Mar 21, 2022 · 2 comments

Comments

@myl7
Copy link

myl7 commented Mar 21, 2022

🐛 Bug Report

When using entity encoding in JSX like &apos;, i18next-parser can not recognize it and convert it to ' in the extracted keys, causing <Trans> without i18nKey can not select the translated value.

To Reproduce

A minimal reproducible example is available on myl7/i18next-parser-mwe

Expected behavior

<Trans>I&apos;m myl7!</Trans> should be extracted as the key I'm myl7! other than literally I&apos;m myl7!

Your Environment

  • node -v: v17.7.2
  • i18next --version: 6.0.0
  • os: Linux
@nicegamer7
Copy link
Contributor

Fixed by #892.

@karellm
Copy link
Member

karellm commented Aug 24, 2023

Should be fixed as of 8.7.0

@karellm karellm closed this as completed Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants