Another thing that doesn’t match up with my experience: https://github.com/fulcrologic/statecharts/blob/a2c6c9150ecf396dd1f9c79c355d7406541051ff/src/routing-demo2/com/fulcrologic/statecharts/routing_demo2/chart.cljc#L36 this seems to pull token and user from event-data but in my experience (using async execution model), is that the event-data contains only 1 key: :fulcro/mutation-result and then you also have to drill down into :body key to get that information
Event data is meant to be the data sent WITH the statechart event…as in via a send. It has nothing to do with mutations.
That said…I think that was an AI-generated demo…don’t remember. Could just be wrong.
The routing stuff is “in progress”. I’m using it on a production product, and it will be fixed up as we find issues.
I do have a bit of an issue connecting statecharts with UI/render tree sometimes.
Biggest showstopper for my dev workflow right now is that these com.fulcrologic.fulcro.dom macros fail when I load CLJC namespaces with these on CLJ side. Are they supposed to not be used in CLJC namespaces (the namespace itself is cljc so that’s why I am a bit confused)
^^^ I answered this on your other thread.