You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shadeglare opened this issue
Sep 22, 2015
· 2 comments
Labels
By DesignDeprecated - use "Working as Intended" or "Design Limitation" insteadCanonicalThis issue contains a lengthy and complete description of a particular problem, solution, or design
This is an unfortunate side effect of syntax ambiguities. You need to either have an extends clause or multiple type parameters. You can write an extends clause that is functionally equivalent (albeit annoying):
danquirk
changed the title
Typescript TSX and generic parameters
Generic arrow functions and JSX
Sep 22, 2015
danquirk
added
By Design
Deprecated - use "Working as Intended" or "Design Limitation" instead
Canonical
This issue contains a lengthy and complete description of a particular problem, solution, or design
labels
Sep 22, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
By DesignDeprecated - use "Working as Intended" or "Design Limitation" insteadCanonicalThis issue contains a lengthy and complete description of a particular problem, solution, or design
Typescript introduces support for the JSX syntax. So I have an expression that works quite well with traditional *.ts files but no with *.tsx ones:
The text was updated successfully, but these errors were encountered: