As a developer, I want dependency graphs to remain readable with many classes so that I can understand code structure #176
Description
Situation
When the target code has many related classes (~30), the Mermaid classDiagram in the code analysis output becomes too small to read. Class names and relationships are illegible.
Example: A batch action class with 30 related classes produced a dependency graph where all text was unreadably small.
Pain
Developers cannot use the dependency graph to understand code structure when the target code has many dependencies, which is often the case for complex batch processes and actions.
Benefit
- Developers can always read the dependency graph regardless of how many classes are involved
Success Criteria
- Dependency graph remains readable when there are 30+ related classes
- At least one of the following approaches is implemented:
- Limit to top N most important classes (e.g., exclude Nablarch standard classes)
- Collapse Nablarch framework classes into a group node
- Split into multiple diagrams by layer/category
- Approach is documented in the workflow