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.
Adds support for unescaping the
/
character. This is one of the characters that i18next itself escapes so I think this is a must.This fixes #1487 which is closed but not fixed.
Note I have only handled exactly
/
, case sensitively. This is what i18next's escaper produces so it's enough to fix the issue. Handling case insensitivity would be a further improvement, though this applies to some of the existing codes too. It's not completely trivial. For example, some entities support all-lowercase and all-uppercase versions but not mixtures, and some only support lowercase. For example,&
and&
are both valid versions of the ampersand, but&aMp;
is not. However for ellipsis, only…
is supported,…
is not. The numeric codes like/
appear to support any mixture of case.Checklist
npm run test
Checklist (for documentation change)