-
-
Notifications
You must be signed in to change notification settings - Fork 645
test(transformer/using): failing test for class name #9678
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
test(transformer/using): failing test for class name #9678
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. |
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.
good find! - out of interest, how did you notices this issue, was it just from reading code, or testing or something else?
890413f
to
9743ebb
Compare
24ebeb0
to
e136646
Compare
Merge activity
|
9743ebb
to
acac461
Compare
Add a failing test for `using` transform where exported class has a reference to itself within the class body, and the external class binding is mutated. This is something of an edge case, but it'd be ideal to handle it correctly. Babel has the same bug: babel/babel#17172
e136646
to
4cee555
Compare
Reading the code. But I'm familiar with these edge cases from working on the class properties transform. We've found during past months on transformer that Babel's test cases often don't cover as much as you'd like. Sometimes there are bugs in edge cases which are rare in practice, so no-one has noticed. But also some things are really simple to do in JS, so Babel probably didn't see the need to add tests for things which are obvious - but they're not nearly as simple or obvious in Rust. So we've had to add quite a lot of extra tests on some transforms. |
acac461
to
26499ec
Compare
4cee555
to
76df73e
Compare
Add a failing test for `using` transform where exported class has a reference to itself within the class body, and the external class binding is mutated. This is something of an edge case, but it'd be ideal to handle it correctly. Babel has the same bug: babel/babel#17172
26499ec
to
664c6f8
Compare
76df73e
to
4dc32db
Compare
Add a failing test for
using
transform where exported class has a reference to itself within the class body, and the external class binding is mutated.This is something of an edge case, but it'd be ideal to handle it correctly.
Babel has the same bug: babel/babel#17172