Community
Participate
Working Groups
I20031007 + Core v375 Test case: public class TestClass { public void foo() { class A { } A a= new A(); } } Search for A. You don't get any reference
Same is true for members declared in local types. Philippe, is there anything we can do for M4. This bugs result in funny results when doing refactorings on local and anonymous types.
Dirk, this isn't yet supported. The only action to take for M4 is to disable such actions until we support them.
Disabling all the action is a pain. So we will keep them enabled and move all PRs to Core ;-). I think people will not use refactoring very frequently to refactor local types. They aren't very common anyway and the side effects are very local.
Kent, will this be in for M5 ?
And we will move them all back to UI :-) Note there is no time to implement this for M4. This is not a regression as this never worked before.
I am not saying that this is a regression but having local types without the rest of the Java API correctly working on them makes them very tricky to use from a client side. Its not only searching. You can't create methods in local types either.
Dirk: Please let us know what other problems you're seeing with local type searches in M5.
The described test case work in M5. They only open issue I am currently aware of is bug 46943. I will open a new PR if I see other cases.
This was fixed in our changes that made it into M5.
Verified.