Currently TypeHelper fails immediately if the TypeNode's type could not be resolved. It could be imrpoved to look into the ExtendsList and ImplementsList if the type node is a type declaration. That way if the type of the main class declaration is unresolved, but it extends a known interface/class (eg a JDK-provided type like Serializable or AbstractList), we may be able to resolve it anyway.
Refs #1668 (comment)
See the current fallback strategy (last line):
if (clazz != null || n.getType() != null) { return isA(n, clazz); } return clazzName.equals(n.getImage()) || clazzName.endsWith("." + n.getImage());RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4