What I try to do it's in my case the service are apollo mutation. I don't want to upfront all the mutation need in this global service. By doing this way I would be able to control the pattern from the component but getting it to work with the global machine.
Could you provide some code to explain what you mean? What are you looking to achieve?
Something like you do with useMachine
But doing it won't work cause this look like create a new instance
What would you expect to happen in this instance? I am still confused by what you're trying to achieve.
You're correct, the above code won't work.
What I try to do it's in my case the service are apollo mutation. I don't want to upfront all the mutation need in this global service. By doing this way I would be able to control the pattern from the component but getting it to work with the global machine.
Why do you want the apollo mutation to be held in the global service? It feels more natural to me to have it in the component where it's used.
I want my service who is global for all the onboarding part to handle the logic and make component quite simple.
Right - I think that's a mistake. Instead, you should keep truly local state local. I would make a state machine inside the component to handle this.
Cause I was trying to implement like you show in the xstate catalog with the multi steps form. Was working well until this issue. Thank you