Added a new Block Diagram#59
Conversation
Added a new Block Diagram view for architecture visualization. uses: mermaid block diagram.
|
@AbdurRafay-Qureshi is attempting to deploy a commit to the braedonsaunders' projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Merged — thank you so much for this, @AbdurRafay-Qureshi! 🎉 The Block Diagram view is a genuinely useful addition: grouping files into higher-level sections (entry, routes, components, backend, services, shared, config) and rendering them with Mermaid makes the architecture far easier to read at a glance than the per-file graph. Nicely done — and thank you for reusing the existing analysis pipeline rather than bolting on a second analyzer, and for shipping it with real tests. A few tiny cleanups folded in on merge, just so you know what changed:
Full suite is green (29/29). Really appreciate the contribution — looking forward to more! 🙏 |
Added a new Block Diagram:
To view to make the repo architecture easier to understand. It creates a Mermaid-based diagram from the existing CodeFlow analysis results. The diagram groups files into higher-level sections instead of showing every file one by one, such as:
Application Entry
Frontend Routes / Views
Frontend Components
Backend / API Layer
Services / Business Logic
Shared / Utilities
Configuration
Content / Data
Uses:
Mermaid.js for rendering the diagram.
Reuses the existing CodeFlow analysis pipeline and file metadata instead of adding a separate analyzer from scratch.
Adds web-app and Next.js route detection for pages, layouts, routes, and framework-specific files.
Works best with web app projects, especially Next.js, React/Vite, and full-stack JavaScript/TypeScript repos.
Should work well with common project folders like:
src/app
pages
components
api
routes
services
middleware
config
Current limitations:
The classification works best for JavaScript/TypeScript web app structures.
Other languages and frameworks may still render, but the grouping may be less accurate.
Dynamic routes, custom aliases, generated files, or unusual folder structures may not always be detected perfectly.