Interest has risen in tandem with the popularity of LLMs. I have worked on these sorts of things as part of internal tooling.
Sometimes these strategies are used to provide LLMs with a greater understanding of your codebase to improve code generation results.
Additionally, techniques which allow humans to visualize the shape of code are being explored as engineers become less familiar with the specific implementation.
I couldn't find architecture.yaml in the repo.
The architecture.yaml file is created in the root directory if you are not able to make that use this command
onboard init --template clean-architecture
recently i read many posts on building a graph for codebase.
why suddenly this becomes popular?
is there a recent breakthough that leads this trend?
Interest has risen in tandem with the popularity of LLMs. I have worked on these sorts of things as part of internal tooling.
Sometimes these strategies are used to provide LLMs with a greater understanding of your codebase to improve code generation results.
Additionally, techniques which allow humans to visualize the shape of code are being explored as engineers become less familiar with the specific implementation.
Is there a way to visualize the code paths on a more meaningful level than line references?
I would think an LLM would be useful for explaining behavior, whereas visualizing code references can be done with no AI at all.
I think i can create a issue and you can contribute this specific feature
Does this tool work with non compiling code?
Nice question you are free to check it!!! If there are any issues in it you can contribute to it
I watched the 1:30 video and didn't see a single code visualization. Not one.
The closest was a "visualization" of a single, unconnected node that can be moved around — all by its lonesome self — on a canvas. For some reason.
You can check out the (onboard map --target ) command which will build a local react app to visualize the codebase