Per-module diagrams missing cross-module dependency arrows #12
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Per-module diagram files (e.g.
aiss_worker.mmd) show zero relationships even when the module imports from sibling modules. Cross-module relationships are captured correctly inoverview.mmdbut dropped when rendering isolated per-module files.Example:
aiss_workerimportsWidgetTypeandWidgetStatusfromcommons, andWidgetJobData --> WidgetTypeappears in overview — butaiss_worker.mmdshows no edges at all.What to build
In per-module rendered files, emit module-level dependency arrows to any sibling module that this module's types depend on. Show them as module-to-module edges (e.g.
aiss_worker --> commons) rather than individual type edges, to keep the diagram readable.Acceptance criteria
aiss_worker --"3 deps"--> commons)Blocked by
None - can start immediately