Handling for `undefined` type about typescript.el HOT 3 CLOSED

Unless you see value in keeping it open for discussion, feel free to close at will. 👍

from typescript.el.

Good observation!

It may just be me, but I think undefined is used much more as a value (for checking incoming stuff) than as a type-declaration.

If we have to choose one (and we have to, because we cannot distinguish those 2 with our current code-base), I'd rather keep it like it is: have it highlighted as a value.

Anyone strongly opposed to this view?

from typescript.el.

It may just be me, but I think undefined is used much more as a value (for checking incoming stuff) than as a type-declaration.

I think there is some code where it could be roughly a one-to-one correspondence, but in general, I agree with your assumption.

If we have to choose one (and we have to, because we cannot distinguish those 2 with our current code-base), I'd rather keep it like it is: have it highlighted as a value.

Agreed; I think of the value defining the type, so having the value take precedence is intuitive.

I'm happy for this issue to be closed, unless you want to leave it open for further discussion.

from typescript.el.