Ryan Cavanaugh comments

Results 613 comments of


                                            Ryan Cavanaugh

Resolving type incorrectly when loop is involved

See https://github.com/Microsoft/TypeScript/wiki/FAQ#circularity-errors-may-occur-in-the-presence-of-circularities The `if` is relevant here because (in the case where it's not *just blank*, which is degenerate), there might be an exit point (`return`, `continue`, `never`-returning function, etc)...

`noUncheckedIndexedAccess` should forbid unsound `Record<string, string>` → `Record<"k", string>` coercion

This would be an enormous breaking change to anyone who just wanted their explicit array access to be bounds-checked, which is what that flag is for.

Properly propagate `ObjectFlags.NonInferrableType` onto non-aliased anonymous object types instantiations

@typescript-bot test it

Properly propagate `ObjectFlags.NonInferrableType` onto non-aliased anonymous object types instantiations

@typescript-bot pack this

Compare optional property flag when comparing against discriminant properties under `exactOptionalPropertyTypes`

@typescript-bot test it

Infer from context sensitive return expressions

@typescript-bot test top999

`silentNeverType` leak through return type inference

Is there a simpler test a mere mortal like me can understand?

JavaScript IntelliSense does not suggest methods added to built-in prototypes

Global merges like this aren't supported; you'll need to use a .d.ts file for this

go to definition panic (windows, wsl)

We could realize use a concrete repro for this. Do you have steps that reliably cause it?

TS2742 “The inferred type of 'default' cannot be named” with ESLint `defineConfig`

(this response was auto-generated) ## FAQ Responses ### The inferred type of "X" cannot be named without a reference to "Y". This is likely not portable. A type annotation is...