Milos Djermanovic
Milos Djermanovic
@amareshsm are you still working on this?
This was discussed several times as an enhancement to this rule (e.g., https://github.com/eslint/eslint/issues/12248, https://github.com/eslint/eslint/issues/12255, https://github.com/eslint/eslint/issues/12427), but it didn't reach a consensus. Since this wasn't considered a bug, I think it...
Can we consider removing support for using RuleTester without a testing framework? In other words, can we remove [`itDefaultHandler`](https://github.com/eslint/eslint/blob/5d65c3bc1e514ed07406c502437a1642913b27ed/lib/rule-tester/rule-tester.js#L325) and [`describeDefaultHandler`](https://github.com/eslint/eslint/blob/5d65c3bc1e514ed07406c502437a1642913b27ed/lib/rule-tester/rule-tester.js#L343)? With async parsing, `Linter#verify()` and thus rule tests will...
RuleTester uses `Linter#verify()`. If parser returns a promise, then `Linter#verify()` must return a promise too. I assume we don't want to maintain both sync (e.g., `Linter#verifySync()`) and async linting because...
> Eslint spent most of its time in parsing files. A javascript parser written in go or rust can potentially improve the the performance of eslint. However this is not...
This is doable, but seems very complicated. Pattern should not contain anything that matches surrogate code units. That includes `.`, `\D`, `\S`, `\W`, negated character classes, etc. Ranges should be...
Ideally, the rule would autofix regular expressions that will have the same behavior with the `u` flag. For those that will have different behavior, the rule could provide suggestions with...
> > However, I think that the suggestion message (or the error message itself) should state whether the behavior will change. > > I think this is asking too much....
It isn't implied. Suggestion can retain the same behavior, but it isn't autofix when it doesn't seem that the behavior was intended. In core rules, we have 3 suggestions that...
Since we have accepted the same change in the `no-misleading-character-class` rule (https://github.com/eslint/eslint/pull/15279), it makes the most sense to accept this change as well.