i18next-parser icon indicating copy to clipboard operation
i18next-parser copied to clipboard

Published 20 hours ago • verified publisher icon i18next

Entity encoding is not recognized by the lexer

Open myl7 opened this issue 2 years ago • 0 comments

🐛 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

myl7 avatar Mar 21 '22 19:03 myl7