This looks really cool! I’ve piddled with something like this using mermaid charts, but this takes it up a level. Do you offer access to the code behind the tool?
They're generated from source code using a combination of static analysis + llm analysis. They're not editable per se, but you can update them when you edit your code.
It identifies telemetry, accessors, and other trivial code and strips them out of the graph. The idea is to retain architecturally relevant parts of the code.
This looks really cool! I’ve piddled with something like this using mermaid charts, but this takes it up a level. Do you offer access to the code behind the tool?
It's a bit like a (simplified) version of Ilograph[0]. Are these editable, or strictly LLM-generated?
[0] https://www.ilograph.com
They're generated from source code using a combination of static analysis + llm analysis. They're not editable per se, but you can update them when you edit your code.
I love this! It's relatively simplistic and would be a really fun tool to use during lectures.
How does it decide which call graphs to include? In a typical project there can be many and these graphs seem to be a small subset.
It identifies telemetry, accessors, and other trivial code and strips them out of the graph. The idea is to retain architecturally relevant parts of the code.
I wish something like this could trace also data flow in a program.
Something I do have in mind. Do you have an idea of the kind of UX you'd like to see?
I would be interested in this too if you ever build it.
Only naïve ones I'm afraid, such as a heap view.
How u make this??