Skip to content

Fix 8549: Using variable as Jsx tagname #9337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yuit merged 11 commits into from
Jun 24, 2016
Merged

Fix 8549: Using variable as Jsx tagname #9337

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
24f3f18
Parse JSXElement's name as property access instead of just entity nam…
Jun 23, 2016
49957a1
wip - just resolve to any type for now
Jun 23, 2016
1369108
Resolve string type to anytype and look up property in intrinsicEleme…
Jun 23, 2016
2e39d1a
Add tests and update baselines
Jun 23, 2016
d5976a5
Merge branch 'fix8549' of https://github.com/Microsoft/TypeScript int…
Jun 23, 2016
e117d02
Remove unneccessary comment
yuit Jun 23, 2016
7a3f88a
wip-address PR
Jun 23, 2016
0e17ac8
Address PR
Jun 24, 2016
cc4a5c7
Add tets and update baselines
Jun 24, 2016
ae38ea5
Merge branch 'fix8549' of https://github.com/Microsoft/TypeScript int…
Jun 24, 2016
d07b27e
Fix linting error
Jun 24, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fix linting error
  • Loading branch information
Kanchalai Tanglertsampan committed Jun 24, 2016
commit d07b27efc62b6a7341aa635776fed73271ea9762
2 changes: 1 addition & 1 deletion src/compiler/checker.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9843,7 +9843,7 @@ namespace ts {
if (indexSignatureType) {
return indexSignatureType;
}
error(node, Diagnostics.Property_0_does_not_exist_on_type_1, stringLiteralTypeName, "JSX." + JsxNames.IntrinsicElements)
error(node, Diagnostics.Property_0_does_not_exist_on_type_1, stringLiteralTypeName, "JSX." + JsxNames.IntrinsicElements);
}
// If we need to report an error, we already done so here. So just return any to prevent any more error downstream
return anyType;
Copy link
Copy Markdown
Member

@DanielRosenwasser DanielRosenwasser Jun 23, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't look like you return anyType/unknownType if you couldn't find an intrinsicElementsType for a string literal.

Why not make it

if (intrinsicElementsType === unknownType) {
    return unknownType;
}

Copy link
Copy Markdown
Contributor Author

@yuit yuit Jun 24, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is actually intended that if intrinsicElementsType === unknownType then you just fall through and check for the construct/call though, arguably we should actually return unknownType instead

Expand Down