Cyclical `always` transitions result in "Maximum callstack exceeded" error about xstate-tools HOT 6 CLOSED

For those following along at home, it worked!

from xstate-tools.

Someone in Discord pointed out that inlining the guards makes the error go away. Unfortunately, doing that prevents you from using the visual editor.

from xstate-tools.

Huh, inlining a guard vs referencing a guard should definitely not result in such a behavior difference. This is definitely a bug - and most likely in XState itself

from xstate-tools.

Huh, inlining a guard vs referencing a guard should definitely not result in such a behavior difference. This is definitely a bug - and most likely in XState itself

To be clear, the machine executes properly at runtime regardless of where the guard is defined. It seems the VSCode extension just can't handle cyclic always transitions and for some reason inlining the guard prevents the maximum callstack exceeded error (but inlining the guard might just be causing the extension to fail/abort parsing the machine before the error can happen?).

from xstate-tools.

Found a fix for this. XState was erroring too soon when you didn't provide a guard that was checked as part of an initial state. So we extract a bunch of 'guards to mock' from the machine definition.

By default, we were setting these guards as () => true. But we don't need to. Setting them as () => false works.

from xstate-tools.

(reopening pending @wKovacs64 feedback on a version distributed privately)

from xstate-tools.