TsConfig: flatten type errors. "Advanced Type" errors currently often unreadable. #35246
Closed
5 tasks done
Labels
Awaiting More Feedback
This means we'd like to hear from more people who would be helped by this feature
Suggestion
An idea for TypeScript
Uh oh!
There was an error while loading. Please reload this page.
Search Terms
"Type error read"
"type errors unreadable"
Suggestion
Type checking, and type definitions errors could me made significantly easier to debug by flattening/boiling down the type definitions to something more resembling what developers think of them as.
For this second example, it would be a lot more useful if instead it just showed what the type realistically is, and what it was missing. Ie:
This would be a really nice thing to add to tsconfig.
Use Cases
Almost 100% of the time one works with advanced types. Anything involving unions or (worst of all) utility types creates a wall of text.
Examples
(I'll make a habit of posting all my most unreadable messages here)
Checklist
My suggestion meets these guidelines:
The text was updated successfully, but these errors were encountered: