-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat: TypeScript 4.2 syntax support #3112
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
Conversation
Thanks for the PR, @armano2! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
@@ -374,6 +374,7 @@ export type Expression = | |||
| SequenceExpression | |||
| SpreadElement | |||
| TSAsExpression | |||
| TSTypeAssertion |
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.
this change is unrelated to upgrade of typescript
Will this change also support this syntax? export type Type<T extends number> = `my-id-${T}`;
// Getting error: ^ Parsing error: Type expected. |
Template string types are already supported as part of our TS 4.1 support. If you're having issues, ensure you update your versions. |
Codecov Report
@@ Coverage Diff @@
## master #3112 +/- ##
=======================================
Coverage 92.90% 92.90%
=======================================
Files 315 315
Lines 10709 10699 -10
Branches 3039 3022 -17
=======================================
- Hits 9949 9940 -9
+ Misses 344 342 -2
- Partials 416 417 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
update: |
6892874
to
e27abac
Compare
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.
thanks!
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.
needs to be updated with master
Conflicts: packages/typescript-estree/tests/lib/__snapshots__/semantic-diagnostics-enabled.test.ts.snap packages/typescript-estree/tests/snapshots/jsx/invalid-mismatched-namespace-tag.src.js.shot packages/typescript-estree/tests/snapshots/jsx/invalid-namespace-value-with-dots.src.js.shot packages/typescript-estree/tests/snapshots/jsx/namespaced-attribute-and-value-inserted.src.js.shot packages/typescript-estree/tests/snapshots/jsx/namespaced-name-and-attribute.src.js.shot
@alitaheri is your issue solved? |
@DerZyklop yes version has been updated in patch release 4.16.1 |
@DerZyklop yes, tested it just now. no more errors 👍🏼 |
Ast structure addition:
JSXNamespacedName
will now be generated when jsx namespace is used in jsx attribute or tag nameTSConstructorType
will now support abstract construct signaturesTODO:
JSXNamespacedName
<a:b.c></a:b.c>
and<this:b></this:b>
Jsx namespaced name and attributes microsoft/TypeScript#42963noPropertyAccessFromIndexSignature
[dot-notation] add support for TS4.2'snoPropertyAccessFromIndexSignature
option #3104fixes #2935