Type resolution fails when namespace collision occurs between local Type and lib reference

I have a package private enum that I reference in another class in the same package. Code underlines the enum as unresolved, because there's no import statement. As the two Types exist in the same package, no import is necessary.

The code builds fine with Maven. Also I'm able to use Code to ctrl-click jump to the enum that Code marks as unresolved.

Environment

Operating System: Windows_NT x64 10.0.19042 + WSLv2 + Ubuntu 20.10
JDK version: OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.20.10)
Visual Studio Code version: 1.52.1, Electron 9.3.5

• Java extension version: v0.74.0

Steps To Reproduce

package SomePackage
public enum TypeA {
ENUM_DEF(String s);
...//private fields, constructor, etc.
public toString() { return s;}
}

package SomePackage
public TypeB() {
String enumVal = TypeA.ENUM_DEF.toString();
...
}

Code underlines TypeA as unresolved, because there are other classes in my maven classpath that are called "TypeA". If I perform an "organize import" command, I see the other types in the dropdown but I do not see my own.

If I rename my local enum to be a unique name, Code resolves it fine. Seems to be a problem with the lookup algorithm that underlines errors, because it ignores the local package.

Riproduci la collisione con due tipi Java dello stesso package e un altro TypeA nel classpath Maven, quindi confronta la risoluzione dei tipi, l’organizzazione degli import e la navigazione ctrl-click. È completato quando il TypeA del package locale viene risolto senza un import, mentre i tipi di libreria con nomi simili rimangono distinguibili.