Statecharts

David did you ever publish the "request" statechart from your talk?

Hi all, I'm newbie and apologies for my english. I have a problem with cond/guards in xstate.js.org/viz, if I put the condition as recommended in the documentation I have this error:

Uncaught Error: Unable to evaluate guard 'isIdleOnLogin' in transition for event '' in state node 'toolbar.login': e.predicate is not a function at e.next (2.06c6d969.chunk.js:1) at e.transitionLeafNode (2.06c6d969.chunk.js:1) at e._transition (2.06c6d969.chunk.js:1) at e.transition (2.06c6d969.chunk.js:1) at e.resolveTransition (2.06c6d969.chunk.js:1) at e.transition (2.06c6d969.chunk.js:1) at 2.06c6d969.chunk.js:1 at 2.06c6d969.chunk.js:1 at t.nextState (2.06c6d969.chunk.js:1) at onPreEvent (main.2b5d9a5b.chunk.js:1)

and my state machine is:

whats is the problem ? Sorry for the long message. Thanks in advance.

with inline function works ok

Please post a link to your state machine definition. It is unreadable.

Sorry, I forgot that possibility. I put only one named condition: "isIdleOnLogin", the rest are inline conditions. The link is https://xstate.js.org/viz/?gist=ce1e1b8228dc9738a6c766eb59a2515b. Thanks.

The problem is not only in "viz" page, in an application too persist.

Sorry, I forgot that possibility. I put only one named condition: "isIdleOnLogin", the rest are inline conditions. The link is https://xstate.js.org/viz/?gist=ce1e1b8228dc9738a6c766eb59a2515b. Thanks.

and the problem is not only in "viz" page, in an application too persist.

Sorry, the last post was a my mistake, no problem in application, only with "viz" page.

Help with a state chart--The visualizer is not showing the transitions from some states. I am not sure why it's not showing the transition arrows from epsEmergencyState to epsExtremeState; epsExtremeState to epsRestorativeState, and so on. Any suggestion will be appreciated.

Sorry, I forgot the url link in my earlier message. Here is the URL link: https://xstate.js.org/viz/?gist=87934eed4eb276962a419155d259be01

@zyadav

You used "ON" instead of "on". Property names are case-sensitive, always.

Thank you so much! I really appreciate it.

do statechart enthusiasts have rules of thumb about what level of complexity warrants organizing code with statecharts

I recently thought about that too when I wanted to implement WebAuthn workflow for my users. I think a statechart is warranted in that case already.

Hi, does anyone know how i would go about running a local/development version of the visualizer? Do i clone the xstate repo, or is it something else?

anyone know of a video series of someone building a non-trivial app using xstate? I saw the feedback form one, but I'd like more of the advanced stuff

I know this post is old, but couldn't you just decide based on the event when the promise resolves, like so?

Wow, this community has grown. I need to get back into it!!!!

The earlier the better. Often the complexity comes creeping in, and you don't realize you need a statechart until after it's become complex. I haven't thought much about rules of thumb for deciding when to do it, but I guess when you start nesting if-tests, or when you are refactoring out the if-tests to keep the code understandable or "clean", you might consider ripping out the behaviour and putting it into a statechart.

Yes, you can do that as well.

I'm late to the party, this blew my mind 🤯, Model-Driven Code. This talk in React Rally 2019 was 🔥 ht

@davidkpiano

I knew xstate would be more mainstream, but this is taking it to the next level. Well done, 👏🏻 I wish I were there.