#idea | #graph #codebase It would be interesting to see the codebase as a graph with multiple levels of details, e.g. a view with files as node, when you click on the node you have a view of its content where the symbols are now the nodes. The consistent thing is that you always have the definition of something and its reference in the definition of something else. This should give us a graph of dependencies where we know all the the contributing elements to a feature. ^8f2d3c This seems doable. For the file view, well all files are nodes and then directional links are mad between nodes when their associated file contains one or more file references, aka paths, whether as imports or inside the code as a file descriptor. For the symbols view, each symbol within the file will be given a styled node and references will be indicated as directed links toward the referencing symbol. For calls at the global scope, well the reference is within the file, so the the directed link goes from inside the file to its outer shell. When you click on symbol nodes, they show their code and the links will point directly to where is the symbol within the code. ![[2024-05-31 2024-05-31 01.43.58.excalidraw.png]] %%[[2024-05-31 2024-05-31 01.43.58.excalidraw.md|🖋 Edit in Excalidraw]]%%