Brandon Mills

If there's no good way to have `.gitignore`-style `.eslintignore` alongside flat config, I'd agree we're better off taking this opportunity to drop it than trying to shoehorn it in and...

The first version of indent was just about blocks and statements. We’ve since added on options for a whole bunch of multi line expressions. It seems reasonable to me that...

Marking this as accepted after discussion in today's TSC meeting. Since there are some complex parts here, we'd like to discuss the implementation details in a [new RFC](https://github.com/eslint/rfcs/) before starting...

I’m :+1: to suggestion instead of fix.

Thanks both for the thorough explanations so far. I'm not opposed to a mode that would allow explicit code point escapes. Were this an opt-in rule, I'd say such a...

We discussed this in the most recent TSC meeting, and there's appetite for making this rule's behavior more consistent with modern JS usage. nzakas suggested a `legacy: true` option, but...

This is great! Since this isn't an external API, it's easy to change as we learn, so I agree there's no need for an RFC. Thanks @pmcelhaney!

I'll kick off the discussion by relating an idea @nzakas had in the TSC meeting discussion that led to this issue. This is only one possible approach, so please share...

> @ljharb: each rule should be able to "register" a hook, and only when the rule is going to be invoked Not all rules need these hooks, so hooks should...

After discussing this in the TSC meeting, we're open to an RFC to explore how much complexity this might add. @Brian-Bartels you can find RFC instructions in the [RFC repository's...