-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
fix(ast/estree): fix TSImportType #9670
base: main
Are you sure you want to change the base?
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Ah, I just realized this is being handled in #9665 😅 Closing |
02d03bd
to
e91439f
Compare
CodSpeed Performance ReportMerging #9670 will not alter performanceComparing Summary
|
5bc5313
to
f05e966
Compare
I'm also not clear on if this is needed or not. But, if it is needed, I think you could put Unfortunately we can't avoid custom serializers/deserializers for these kind of cases, but in my view the smaller we can keep them, the better. It's easy for the Rust and JS implementations to get out of sync, and at some point soon we'll also add support for transferring ASTs in the other direction (JS -> Rust), at which point we'll also need to add (1) a JS serializer and (2) a Rust deserializer for all these custom cases. Inevitably it's going to get a bit messy, but it's ideal to minimize that mess as much as we can. PS: Hope you're enjoying the bizarre torture of writing the |
attributesKeyword: IdentifierName; | ||
elements: Array<TSImportAttribute>; | ||
} | ||
|
||
export interface TSImportAttribute extends Span { |
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.
Can this be omitted from the typegen? (with TSImportAttributeName)
TSImportType.options
asObjectExpression
#9663