Kirk Waiblinger

So, is this actionable? My interpretation of the conversation so far is: With the "property" option enabled, when encountering method signatures that make use of the `this` type (except possibly...

Actually, now that I think about, there's an argument that _both_ should flag by default. No matter which branch of `if (x && y)` is truthy/falsey, either one will _always,...

@JoshuaKGoldberg > > there's an argument that _both_ should flag by default > > Agreed. Right now, `if (Boolean("don't flag") && Boolean("should flag!")) {}` does report both of them with...

https://github.com/typescript-eslint/typescript-eslint/issues/8453 does bring up an interesting additional context that could be checked. Might be more worthwhile of a rule if there's it's more generally to prefer `.some()` and `.every()` wherever...

Confused by the CI failure, looking for advice on how to resolve it

> Great improvements 👍 ❤️ > Do you know why we have so many precedence levels defined for what MDN defines as "precedence 2"? I personally do not know for...

I'm big +1 to this, but, I am also concerned that the current rule is too opinionated, and would cause a lot of unnecessary flagging in existing codebases. I'd propose...

> so why is extra **_initial_** flagging bad? Mostly, it's just that I would be scared we'd not get the rule into a recommended preset at all if we reawaken...

If backlash that it's too opinionated where it doesn't affect the outcome of execution is not a concern, then everything I've said is moot! 🙂

I'm curious - are you able to use `dom.iterable`? I would think any `es2022` target should support it, but I've never been totally certain on when you can and can't...