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
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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