We are often challenged with the maintenance of existing projects that were developed by other agencies, or a new developer arrives and we need to quickly bring them on board. The complexity of legacy projects can be very high and the risk of breaking existing logic is something we want to avoid.
One way we like to look at a project before diving into the code is through its data structure. The different entities and their relations can tell us a lot about the business logic of the site and its internal logic. We assumed that if we could easily generate a graph with all the bundles, entities, and their relations this complex task would be easier.
Having done this for a while now, I believe our assumption was right. Taking our open-source Productivity project (Gizra’s internal ERP/Project management system) as an example, it’s much easier to look at the following graph and understand that
Github Issue bundles are pointing at a
Project, which in turn points to an
Github Issue can also reference itself.
Thanks to Damien Tournoud’s previous work getting the graph out wasn’t too complicated. His sanbox module already output the entities and bundles. It was merely missing the relationships between them, and a UI to display the graph.
So, standing on the shoulders of giants, we’ve adapted the code and now have an Entity Relationships module.
There are two interfaces to get the graph:
Use this from the command line to get an image:
drush entityrelations | dot -Gratio=0.7 -Eminlen=2 -T png -o ./test.png
Craft your URL according to your needs:
- All the entities at
- Only the node’s bundles
- A simplified graph of the node’s bundles, with no fields at
Simple, but powerful.