You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is a .mutation value in the response data, the corresponding mutation is called with the name SOCKET_[mutation value]
This however, is not true. It gets called exactly like the .action case:
If there is an .action value in the response data ie. action: 'customerAdded', the corresponding action is called by name
I personally like this better (calling the mutation directly without the need for the mutation name to start with SOCKET_) but the documentation is wrong either way.
The text was updated successfully, but these errors were encountered:
The documentation says:
This however, is not true. It gets called exactly like the .action case:
I personally like this better (calling the mutation directly without the need for the mutation name to start with SOCKET_) but the documentation is wrong either way.
The text was updated successfully, but these errors were encountered: