-
Notifications
You must be signed in to change notification settings - Fork 194
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
Import not updated for nested enum class #379
Comments
Same issue exists if |
ready to test Fully- or partially-qualified names within the class or script body are a bit trickier. They may contain extra whitespaces and have some other complications that I did not deal with quite yet. |
Hi Eric, I tested this with 2.9.2.xx-201711140121-e46 but the behaviour I see is not correct. After renaming package test9
import test9.Outer2.MyEnum
class GroovyClass {
void doSomething() {
MyEnum myEnum = MyEnum.A
}
} This is what I get instead: package test9
import test9.Outer2.Outer2
class GroovyClass {
void doSomething() {
Outer2 myEnum = Outer2.A
}
} In other words, not only the |
Bummer. I forgot to test with non-star imports. My final tweaks must have reversed a previous check that I had to prevent this matching which I was seeing early on.
|
ready to re-test |
Seems to work fine now with 2.9.2.xx-201711150348-e46, thank you! 👍 |
Consider the following Java class:
And the following Groovy class:
Now refactor
Outer
class and rename it toOuter2
.The following line in
GroovyClass
is not updated:import test9.Outer.MyEnum
The text was updated successfully, but these errors were encountered: