Francesco Trotta

Currently, `RuleTester` doesn't complain if a rule has no invalid test cases. If this change is implemented straight as proposed, we will be ensuring that fixable rules actually provide a...

> The usecases for that sort of thing are pretty niche mind you. I think that it is literally limited to unused vars. Yeah, there are a few use cases...

If we aren't going to make any changes to `RuleTester`, I agree it would be good to clarify the fact that the expected `output` of single test cases does not...

It seems that [RFC 93](https://github.com/eslint/rfcs/pull/93) was closed because of limitations in the VS Code ESLint extension, one of the "interactive environments" mentioned in the motivation section, which would not have...

> Where we're at here is deciding whether we want to deprecate these two rules: > > * `multiline-comment-style` > > * `line-comment-position` I think it makes sense to move...

I am able to reproduce this issue. Marking as accepted as there is agreement that this is a bug in the comments to #17560.

> If user runs `eslint --cache --quiet`, only errors will be stored in the cache because rules set to warn were not run. If the user then runs just `eslint...

> > Maybe we could extend that function to also include the `quiet` setting in the hash. > > A problem with this solution is that the `quiet` setting is...

Thanks for the RFC @softius. Can you please sign the CLA as requested in [this comment](https://github.com/eslint/rfcs/pull/119#issuecomment-2068954974)?

Thanks for this RFC @aryaemami59! Could it be that Jiti doesn't transpile top-level `await` expressions properly? For example, the following config is throwing an error for me: ```ts // eslint.config.mts...