Brandon Mills
Brandon Mills
When you say merge multiple path objects, do you imagine it would take the union of all `importNames` and use just the last error message? From a quick skim of...
> I’d argue that is the expected behavior. Agreed, cool. > This, however, looks like a breaking change, because now-unused config entries will become used and can produce new lint...
Reading through the original rule proposal, specifically how it differs from https://github.com/eslint/eslint/issues/8447, it seems to me the intention was always to make this about significant digits of precision, but we...
This is a similar issue to #13634. I believe we can fix both in semver-minor changes.
:+1: from me. `eslint-release` was a great automation tool when other options weren't so well-developed. Now that well-supported community-maintained options are available, it would be nice to remove the overhead...
The TSC accepted this change in Thursday's meeting. We'll do this as a phased migration so we don't disrupt releases.
We're still in the middle of this migration right now, where we're using our own tooling adapted to work with conventional commits. The checklist at the top has a couple...
@mdjermanovic's suggestion looks good!
#15240 proposes catching bidi characters and homoglyphs. It sounds like we should also catch a third category of invisible characters like `\u3164` and `\uFFA0`. `no-irregular-whitespace` already catches a bunch of...
I agree that a custom processor would be the way to go. It would have specific knowledge of the library's semantics and know which function bodies to include in the...