Can't ignore "–"

[3raser95]

I've been trying to ignore the string – but the rule doesn't seem to be working for it. I've used this rule:
"i18next/no-literal-string": [ 2, { "words": { exclude: ["–", "Option"] } } ]

With this rule the Option gets ignored fine inside a span element, but – inside span doesn't get ignored. As far as I know the & and ; don't have a special meaning in regex so it should work as is. Is this a bug or am I doing something wrong?

[3raser95]

Found out that I need to exclude "\u2013" even though in my files they are written like – which is quite confusing and I still think it should be fixed.

[edvardchen]

I understand your concern. It will be nice that we can ignore those unicode characters that are not in natural languages. But I don't know if there is a general way to recognize them.

In new version v6.0.0-7 the exclude option can accept regex as params now only if your eslint configuration is written in javascript. You can experiment with regex to see if it's possible. And welcome PR any time

[edvardchen]

It turned out that Babel JSX compiler converts HTML entities into the unicode characters they represent

Babel already maintained a complete list of html entities so that we can just copy them over here

I will fix it in #108