You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried rails-erd and railroady gems and I'm not 100% satisfied with neither of them.
Rails-erd
Seems better well maintained but for this particular project lacks an important feature: different colors in the relationship arrows (there's an issue on the project already)
Seems less well maintained, and with a lot of options by default (and export to svg instead of pdf or image) but has the cool relationships arrows with colors
Both are pretty configurable (as you can see default options are different... one shows fields like id and created_at and the other doesn't show many tables for inherited models.
So my question is do you think it a Database Diagram could improve on-boarding for this project?. Maybe the smallest version possible (hidding as much as possible, only showing the most important models and relationships), but getting to that configuration with either of the gems could get some effort... maybe not worth?
The text was updated successfully, but these errors were encountered:
I've tried rails-erd and railroady gems and I'm not 100% satisfied with neither of them.
Rails-erd
Seems better well maintained but for this particular project lacks an important feature: different colors in the relationship arrows (there's an issue on the project already)
Result: erd.pdf
Railroady
Seems less well maintained, and with a lot of options by default (and export to svg instead of pdf or image) but has the cool relationships arrows with colors
Result: models_complete.pdf
Both are pretty configurable (as you can see default options are different... one shows fields like
id
andcreated_at
and the other doesn't show many tables for inherited models.So my question is do you think it a Database Diagram could improve on-boarding for this project?. Maybe the smallest version possible (hidding as much as possible, only showing the most important models and relationships), but getting to that configuration with either of the gems could get some effort... maybe not worth?
The text was updated successfully, but these errors were encountered: