Brad Zacher

It's an array! The tooling just iterates the array, so a then b

@JoshuaKGoldberg i wonder if we should merge this with https://github.com/typescript-eslint/typescript-eslint/issues/5677 It seems like they're doing the same thing, except #5677 covers more cases.

@mahdi-farnia by using types! All of the relevant information is available on the types. You can play around in https://ts-ast-viewer.com to get a feel for how different cases might look....

Any type with an index signature is indexable. Eg ```ts type T = { [k: string]: number} ``` But we should still ensure we disallow string likes and arrays

One other thing to be careful about here is that I don't believe that jest will detect the inter-package dependencies. Which means that a change to the parser wouldn't cause...

That was my thinking too. I've been humming and ha-ing over this and I wasn't sure if this was really something that causes issues in codebases. The big reason it's...

What's really funny here is that TS doesn't narrow your types because of the aforementioned structural typing. When you compare `User | undefined` to `number | undefined`, TS cannot refine...

TS is quite helpful in assignments - it does its best in order to help you **not** shoot yourself in the foot due to its structural typing model. TS knows...

No definitely - I understand the intent of the issue and your goals. What I'm saying is that how can you tell that a check like `(string | undefined) !==...

Based on the above discussion - I don't think this rule is ultimately going to be feasible to build this rule. I can only see it "working" if we completely...