You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
package test;
public interface OuterClass {
public class InnerClass {
}
}
Mapper.java
package test;
public class Mapper {
public void te() {
new InnerClass
}
class WrapperOne {
public void test() {
new InnerClass();
}
}
}
For new InnerClass| , there is no quick-fix to import import test.OuterClass.InnerClass so that InnerClass could be referenced directly as new InnerClass();. Another option would have been to qualify new InnerClass() as new OuterClass.InnterClass() but I'm not sure if there's a quick-fix for this.
The completion engine doesn't suggest new InnerClass() even though unresolved types can get suggested and are automatically imported (eg. new ArrayList|) when unresolved.
I seem to recall that the unresolved import quick-fixes do use completion engine API (on constructors) to produce suggestions so maybe the bug is in completion.
The text was updated successfully, but these errors were encountered:
From redhat-developer/vscode-java#3815 (reproduced in Eclipse)
OuterClass.java
Mapper.java
new InnerClass|
, there is no quick-fix to importimport test.OuterClass.InnerClass
so thatInnerClass
could be referenced directly asnew InnerClass();
. Another option would have been to qualifynew InnerClass()
asnew OuterClass.InnterClass()
but I'm not sure if there's a quick-fix for this.new InnerClass()
even though unresolved types can get suggested and are automatically imported (eg.new ArrayList|
) when unresolved.I seem to recall that the unresolved import quick-fixes do use completion engine API (on constructors) to produce suggestions so maybe the bug is in completion.
The text was updated successfully, but these errors were encountered: