Similar to how the database schema for a table is generated and placed at the end of a model file after a migration, run the erd gem's command to build a new ERD diagram every migration. This is real helpful for those building a mobile app to see at a glance the entities and their hierarchy, as well as anyone jumping into a project after its initial creation.
Also, we should include a default .erdconfig in Voyage at the start as well. I've been using this:
Similar to how the database schema for a table is generated and placed at the end of a model file after a migration, run the
erd
gem's command to build a new ERD diagram every migration. This is real helpful for those building a mobile app to see at a glance the entities and their hierarchy, as well as anyone jumping into a project after its initial creation.Also, we should include a default
.erdconfig
in Voyage at the start as well. I've been using this:I imagine the exclude list will expand / change, but it's a starting point for now.