Elaborate on non-portable types #53764
Labels
Experience Enhancement
Noncontroversial enhancements
Help Wanted
You can do this
Suggestion
An idea for TypeScript
Milestone
Suggestion
π Search Terms
type annotation elaboration not portable cannot be named
β Viability Checklist
My suggestion meets these guidelines:
β Suggestion
To improve DX this error message should mention what part of the type is not portable:
Perhaps it could even suggest what export is missing in the referenced module.
I've experienced a situation in which an inferred return value was an object with multiple properties and some nesting. One of its properties had a non-portable type. It would be a huge improvement if the error message could mention which property is not portable (let's say
user
in this example) and it would be even a bigger improvement if the name of the said type would be mentioned (let's sayUser
in this example)The text was updated successfully, but these errors were encountered: