How andrea-salvatore/er_diagram works
E/R Diagram is a cross-platform, diagram-as-code application: users describe relational schemas as text, and the app validates and lays them out as an ER diagram rendered on a canvas. The README documents the parser-to-model-to-layout-to-renderer boundaries, including routing and interaction capabilities. The only Dart source path in the tree is lib/main.dart; implementation details for these subsystems were not sampled, so the graph reflects documented architecture rather than verified internal calls.
Main entry points: main.dart Typed graph model
Components 11
Schema input
- Flutter application
lib/main.dart - Lexer and parser
lib/main.dart
Model and geometry
- Typed graph model
lib/main.dart - Semantic checks
lib/main.dart - Topological ordering
lib/main.dart - Layer assignment
lib/main.dart - Coordinate layout
lib/main.dart - Orthogonal routing
lib/main.dart
Rendering and interaction
- Canvas renderer
lib/main.dart - Diagram interaction
lib/main.dart
Other components
- Schema author
Connections 10
- Schema author → Flutter application: enters schema
README.md - Flutter application → Lexer and parser: submits text
README.md - Lexer and parser → Typed graph model: builds model
README.md - Typed graph model → Semantic checks: checks semantics
README.md - Typed graph model → Topological ordering: provides graph
README.md - Topological ordering → Layer assignment: orders layers
README.md - Layer assignment → Coordinate layout: assigns positions
README.md - Coordinate layout → Orthogonal routing: routes edges
README.md - Orthogonal routing → Canvas renderer: supplies layout
README.md - Canvas renderer → Diagram interaction: handles input
README.md