The current setup of QQmlJSRegisterContent and QQmlJSScope, mediated through QQmlJSTypeResolver is too inflexible. We come up with more and more relations between types that need to be shoehorned in there. What we actually is a graph of types. The nodes are QQmlJSScopes, and the edges are relations between them, such as:

1. stored in
2. generalized to
3. read as
4. retrieved as property x from
5. retrieved as return type from call to x on
6. etc

Modeling the type information as such a graph would allow us to search for relevant information in a more natural way, without dragging the type resolver and all its tables around all the time.