fastapi-voyager, from left to right, is tag, routes(apis) and response_models, it indicates the internal relationship between routes, which can help developers/PO easily figure out the data structure.
in voyager their relationships are visualized and very close to the source code.
those are clusters based on modules, you can swith off by toggle 'show module cluster'
the goal is to make the dependencies clear for developers, and figure out the potential impacts from one node to others.
pydantic-resolve is just another my project to make the process of data composition close to ER model and get rid of glue codes like 'for loops'.
The tangled mess kind of picture is still sometimes useful: you can roughly see bunches grouped, and notice things that are all over the place.
It's 2025, I don't want to look at a giant hairball. At top level, give me a summary, reveal detail as I drill down.
Am I using this as a reference? The search looks promising, I can follow thru and find specifics on a particular item I am after.
and in local env, you can 'really' open it in vscode.
pick tag/routes at left panel, and see subgraphs
double click to see field table and source code, click link to see source code in github
click focus to hide other nodes.
...