Description
Apologies if you don't like support questions as issues, let me know where to put it if that's the case.
Given a project with 2 main concepts: "controllers" and "repositories", can I generate a "controllers" graph that show all controllers and their up- and downstream dependencies? I'd then make two graphs, one for each concept.
Context
I'd like to target a specific concept so I can open the "controllers" graph and inspect everything relating to that concept, e.g. which tests depends on them and which modules are used by controllers. That would be a handy way to get an overview. I also generate a full module graph with all dependencies but it's overwhelming so I'm looking for ways to divide-and-conquer the visualization.
Expected Behavior
I thought by making a permissive config file with includeOnly: "(src|test)"
and running the CLI with a directory-argument of src/controllers
it might "target" controllers and draw in all connected nodes. I do end up with downstream nodes so it's close, but no upstream nodes are visible.
Considered alternatives
it could be I'm overthinking this, so please consider this an attempt at a friendly question rather than an outright feature request.
And many thanks for making your library available.
Metadata
Assignees
Projects
Status
released