Statecharts

Statecharts are a precise, visual way of modeling the behaviour of complex reactive systems. They describe how things work, and can help you get your code doing exactly what you want.

Channels

Chat

Team

Statecharts watercooler

March 7, 2019 at 5:55am

Erik MogensenTeam

@mogsie

Statecharts watercooler

March 7, 2019 at 5:55am

Show previous messages

December 21, 2020 at 4:12pm

Sébastien Wauquier@fellowseb

4:12pm

joshuaaron@joshuaaron

what's the difference between spawning an actor and spawning a machine? by the looks of the docs they look identical? actors machine

From my understanding one can describe the behaviour of an actor using a callback, a promise, an observable or a machine. The first docs link you mention simply uses the machine case to describe the general concept.

5:05pm

Hey all ! I recently made my first statechart using xstate, This statechart isn't directly modelled in the UI layer, as it has two distinct UIs to drive simultaneously. I'm now trying to make it easier to understand in the visualizer by regrouping states that share transitions in compound states (clustering, as this page describes it. While statechard.github.io doesn't make the distinction, xstate lets me choose between creating hierarchical state nodes and invoking other machines/actors. Do you have any guidelines about when to prefer one method over the other ? My guts tell me it's a modularisation/boundaries problem. Also having separate machines allows isolation of the context data. But feel free to correct me.

In addition to this, when creating compound states, I find myself adding more states that don't have a representation in the UI; like final child state nodes. How does a normal xstate + react app handle those to make no re-render happens ?

December 22, 2020 at 1:23am

Sébastien Wauquier@fellowseb

1:23am

For those passing by, I think I'm finding parts of answers to my questions in this thread about decoupling statecharts and views :