eslint-plugin
eslint-plugin copied to clipboard
lingui
Set of ESLint rules for Lingui projects
I'm using lingui/no-unlocalized-strings and it's showing warnings about attributes that shouldn't be localized, for example: ``` // getting error disallow literal stringeslint(lingui/no-unlocalized-strings) ``` usually I would solve it with `ignoreAttribute`,...
If i have `ignoreProperty: ["ignoreThis"]` option set for `no-unlocalized-string`, it would be very helpful to also ignore any strings for subkeys under the ignored property. ```ts const obj = {...
When using the rule "no-expression-in-message", I would like to have warnings for `` tags just like they warn when using `t` 
Here's a simple example illustrating what I think should *not* be flagged by the `no-unlocalized-strings` rule ```js const obj = { "key with space": 5 }; const value1 = obj["key...
Property should be ignored. This only happens inside an object literal, but does not work when accessing a specific property of an object. My rule: ``` "lingui/no-unlocalized-strings": [ 2, {...
There are times when the built-in checks in `no-unlocalized-strings` are wrong. i.e. `` is considered valid due to uppercase check. In our case, a lot of titles are uppercase and...
Let's collect here rules which might be helpful.
"lingui/recommended" This is my proposition for recomended set: ```json { "rules": { "lingui/missing-lingui-transformation": 2, "lingui/t-call-in-function": 2, "lingui/no-single-varibles-to-translate": 2, "lingui/i18n-only-identifiers": 1, "lingui/no-single-tag-to-translate": 2, "lingui/no-trans-inside-trans": 2, } } ``` Explanation: Almost all...
Using this plugin with flat config is a bit cumbersome atm. It would've been nice to update it to the most recent plugin structure and provide couple flat config examples.
Hi there I am seeing a bit of unexpected behavior and not sure if it's something in my configuration or a misunderstanding on my part. My expectation would be that...
