-
Notifications
You must be signed in to change notification settings - Fork 1.7k
JS: Support Typescript 5.6 #17164
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.
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
JS: Support Typescript 5.6 #17164
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
The only relevant change seem to be the arbitrary module identifiers.
Just one minor nit how we specify the version of TypeScript we use.
I've started some DCA runs. I'll comment here when they are done.
Co-authored-by: Erik Krogh Kristensen <[email protected]>
…deql into sidshank/ts-5.6-update
isNamespaceExportNode | ||
? Collections.singletonList(convertNodeAsIdentifier(exportClauseNode.getAsJsonObject())) | ||
: convertChildren(exportClauseNode.getAsJsonObject(), "elements"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a test for this specific syntax?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do. I'm taking a look at convertImportDeclaration
to see if I need to make similar changes there. Once I figure that out (and make the changes if necessary), I'll add tests.
Closing in favour of: #17433 |
This pull request enables CodeQL analysis of code using TypeScript 5.6 features. Notably, the use of arbitrary import/export specifiers is now supported. Ref 1, 2
Release announcement here: https://devblogs.microsoft.com/typescript/announcing-typescript-5-6/