What problem does this solve?
An example of the problem is large documentation with specs and a technical specification.
Currently, the graph builds nodes where only the header is present in the code snippet. That’s good, but not enough. And it doesn’t build edges based on file references — that’s a big drawback.
Proposed solution
I propose that we first implement support for md links = edges.
Example of link search: \]\(<([^>]+?\.md)>\)
Alternatives considered
Right now, I’m creating a metadata file for documentation that describes reference links as functions in TS and saves them next to the documentation blocks. This is a working solution, but it’s not ideal and requires constant manual regeneration of the .ts file.
Confirmations
What problem does this solve?
An example of the problem is large documentation with specs and a technical specification.
Currently, the graph builds nodes where only the header is present in the code snippet. That’s good, but not enough. And it doesn’t build edges based on file references — that’s a big drawback.
Proposed solution
I propose that we first implement support for md links = edges.
Example of link search:
\]\(<([^>]+?\.md)>\)Alternatives considered
Right now, I’m creating a metadata file for documentation that describes reference links as functions in TS and saves them next to the documentation blocks. This is a working solution, but it’s not ideal and requires constant manual regeneration of the .ts file.
Confirmations