-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Statemachine errors on send(), possible documentation issue #534
Comments
I should add, this issue still occurs when I use an example statemachine from the statemachine guide. |
I've encountered the same issue (and know I have previously encountered it as well, but do not recall the resolution). I have refactored a pre-existing state machine, and this refactoring introduced this bug when running against a mock Overmind instance in a unit test - but not in the live app. I am having a lot of trouble tracking down precisely which change is responsible. |
https://codesandbox.io/s/overmind-counter-forked-d7o1h?file=/src/index.js
I am using a StateMachine based on what I found in the documentation, and depending on how I try to instantiate it, it will fail when I call send() with either
state.send is not a function
(if my config includes the state machine as state: refresher.create...) ortree.enableMutations is not a function
if I have included the machine in a namespace or a field ofstate
.I noted that the statemachine guide included useOvermind. Hasn't that been removed? I did check to make sure I was on the Overmind 28 docs.
The text was updated successfully, but these errors were encountered: