Types are messy in both their construction and their representation.
In the JSON output of the doc, there should be enough information to be able to build links to types descriptions in the UI, from the return type of an API method for instance. LivedocType should contain such information, for instance a list of AtomicTypes, each containing some sort of ID (like the fully qualified name of the class) to be able to uniquely identify a type, and thus create links.
The hierarchy of type declarations in nested generics should be preserved, so as to be displayed properly.
The current building code is very verbose and bug-prone, we should adopt a more generic approach, and make use of recursion properly
Types are messy in both their construction and their representation.
LivedocTypeshould contain such information, for instance a list ofAtomicTypes, each containing some sort of ID (like the fully qualified name of the class) to be able to uniquely identify a type, and thus create links.