Post

Convince me I am wrong: This should not be a type error, right? - I asserted it’s an object - I am using `?.` for property access www.typescriptlang.org/play/#code/G...

`typeof null === 'object'` so I think you might need to check for null. And then I tend to find 'a' in x more reliable in TS

Right, I know how to work around it. But I am asking: Shouldn’t this be accepted by the type checker (because `null?.a` is perfectly valid)

The issue isn't the null. `object?.a` is not valid!

Why not?

Yes. I know how typescript currently works. I'm claiming that TS should change it's behavior here (hence why I said "this should not be a type error, right?"). I thought you were saying that what I was doing here is wrong at the type theory level, which I don't think is the case.

I disagree and think the type error is correct. How do you propose to change the behaviour? What type should typeof === 'object' give you? It appears that you want it to be `any`

I'm proposing that `o?.x` is not a *type error* if `x` does not exist on o's type.