Open Martin-Luft opened 6 years ago
Thanks for reporting the issue. I will add test for your specific examples and fix the issues. The i18n
rules were recently added, we are still figuring out the correct behavior in some cases.
There is an issue opened concerning the status of each rule #408. In the meantime, maybe can we a this status in our Readme.
I'll update the readme in a sec.
@mgechev you missed the following rules:
import-destructuring-spacing
, pipe-naming
and no-output-named-after-standard-event
.
@mgechev and the rules page (http://codelyzer.com/rules/) doesn't contain:
trackBy-function
and no-output-named-after-standard-event
Should I open a new issue for that?
Yes @Martin-Wegner , you can !
"i18n": [true, "check-text"]
does not work for this examples:or
And can you please explain which codelyzer rules are stable and production ready and which not? For example you said that the no-unused-css rule is not stable (here https://github.com/mgechev/codelyzer/issues/364) and this i18n rule seems to be unstable as well.