Open PriyaBhatia0210 opened 3 years ago
Proposed tactic: (courtesy @rmccue)
Step 1 of this would be to model the state machine using something like XState which can produce a machine-readable version of the state machine in e.g. SCXML.
We can then build atop that and rebuild the state transitions on top of that by unhooking large parts of core and rehooking them in based on the state machine.
Changing the state machine would then be a fairly logical and consistent process, because all transitions would then go via the state machine rather than being hacked around everywhere in core.
This is a decent amount of work, but the largest part by far is breaking down core and rebuilding it. I actually think there's a decent chance we could do this in core itself if it were designed well. If we don't do that, it'll be brittle and require maintenance in every release, plus verification of changes.
Breaking up the technical research required for our Workflows solution into following constituent pieces:
In this issue, we'd like to explore what does the WP state change machine entail for creation of custom transitions.
Requirements
Timebox: 1 day