Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
feat(typescript-estree): support TSv4 labelled tuple members#2378
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Thanks for the PR,@bradzacher! 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 onhttps://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitorsper day. |
17bcfb2
to9d94a36
Compare9d94a36
tofabf2e0
CompareCodecov Report
@@ Coverage Diff @@## master #2378 +/- ##======================================= Coverage 93.10% 93.11% ======================================= Files 285 285 Lines 9125 9134 +9 Branches 2504 2505 +1 =======================================+ Hits 8496 8505 +9 Misses 302 302 Partials 327 327
Flags with carried forward coverage won't be shown.Click here to find out more.
|
longlho commentedAug 12, 2020
This seems to be a breaking change sinceTS@3.x does not have |
See discussion in#2388 |
Uh oh!
There was an error while loading.Please reload this page.
Ref#2260
For simplicity's sake (and because babel has already released their representation), I just went with adding
TSNamedTupleMember
.I was considering doing a big breaking change an introducing a new AST node in here to represent all tuple members, instead of having all of the following as valid tuple members
TSOptionalType
,TSRestType
,TSNamedTupleMember
, and anyTypeNode
.Whilst it will be a much nicer AST to consume, it's probably too large of a change to make...
This PR also updates the versions of babel we test against, and unignores some tests. Doing so uncovered a range bug in
import type Foo from 'foo'
(theImportDefaultSpecifier
's range included thetype
keyword).Finally, I also brought over the compile-time checks added in#2375