Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
fix(ts-estree): align typeArguments and typeParameters across nodes#223
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
fix(ts-estree): align typeArguments and typeParameters across nodes#223
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Codecov Report
@@ Coverage Diff @@## master #223 +/- ##==========================================+ Coverage 96.57% 96.65% +0.08%========================================== Files 51 51 Lines 2455 2455 Branches 370 370 ==========================================+ Hits 2371 2373 +2+ Misses 42 41 -1+ Partials 42 41 -1
|
bradzacher commentedFeb 6, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I was wondering after looking at#222 - why do we have so many optional properties on the AST? I can understand an optional field in the case of interface -> implements where it's not "supposed" to be there. |
armano2 commentedFeb 6, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
those nodes does no contain undefined arrays
this is useful for setting up comments in AST, and without that there is no easy way to determine if comment is |
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.
LGTM
This PR aligns
typeParameters
andtypeArguments
across all nodesfixes:#220