arel VS sipity

Dropping into Arel is an option but keep in mind you'll be relying on a less than public api so expect things to break when moving rails versions. https://github.com/rails/arel/tree/5a75bcaf67613b4241a3223b734ed4dc8526df6c just check your lock file to make sure that's the right arel version

Nothing goes poof in git: https://github.com/rails/arel/tree/e6ff32c6b2698ef9f2d5a9832f08d3683d5116ee

My solution was to perform some ActiveRecord antics. I had previously done extensive antics in my query implementations of Sipity. Fortunately, for the Forem implementation I didn’t need to dive deep into Arel.

My solution was to perform some ActiveRecord antics. I had previously done extensive antics in my query implementations of Sipity. Fortunately, for the Forem implementation I didn’t need to dive deep into Arel.

So I began scratching together an Entity Relationship Diagram of the database tables I would need to encode the complex state machine that began emerging. In implmenenting the state machine in the database, I could make a database change, run it through Graphviz, and print out the current state of the flowchart. Sipity, the state-based collaborative todo application, still chugs along 7 years later. And a few years later, we extracted a major component of it for another application. I have dreams of a proper gem-based extraction, but have never prioritized that effort.