refactor: Fix a bug in reorganize_definitions for uses of foreign types#1732
refactor: Fix a bug in reorganize_definitions for uses of foreign types#1732
reorganize_definitions for uses of foreign types#1732Conversation
018672b to
26ed001
Compare
randomPoison
left a comment
There was a problem hiding this comment.
Can you give a bit of context for what this change is accomplishing and why it's needed, e.g. what bug you're trying to fix? I'm not intimately familiar with reorganize definitions, nor with the CRISP changes that I assume are the motivation for this, and I'm having trouble understanding from the test change what the expected change in behavior is.
In general, it'd be helpful to provide this context in the PR description. Reviewing a change without context is hard and time consuming because I have to do a bunch of digging to figure out the context for myself.
We don't seem to have a bug yet, I can go open one. Stuart reported a crash in |
I'm not sure who else is, other than me. |
reorganize_definitions for uses of foreign types
That's fine, I don't necessarily need a ticket for it, but it'd be helpful if you can explain here what behavior you're trying to change.
That's also fine, I'm still able to review this, and reviewing changes like this is part of building an understanding of the refactorer and this transform. But since I (and others) don't have the context already, it's helpful if you can provide that context. |
kkysen
left a comment
There was a problem hiding this comment.
Could you put the new test code in a new snapshot test? The current one doesn't compile after reorganize_definitions, so it's missing an important part of testing (which would catch this bug). So could you put it in its own snapshot file, initially set .new_expect_compile_error(true), and then remove that in the 3rd commit that fixes the bug?
Otherwise, the changes to the refactorer and to the snapshot LGTM.
26ed001 to
cce4c5b
Compare
a1b7d9f to
03aff27
Compare
That was my original approach, but it seemed like we already put all the tests for a transform in one file? Or should I use |
e1b743a to
354ce9e
Compare
kkysen
left a comment
There was a problem hiding this comment.
LGTM now besides sorting the tests.
354ce9e to
0a0fd75
Compare
Uh oh!
There was an error while loading. Please reload this page.