The reason why the object is not send with the creation is that it gives a notification instead of the actual data - This permits a validation of the required permissions on the server side when client GETs the object(s).
The more I think of it, I think that angular-jsonapi should only have hooks to pass the CUD operations to so that the websocket connection could still be used (and/or handled) for other purposes.
My current implementation sends updates to connected clients when events occur on the server:
Update format:
For a create:
For A change:
For A delete:
The reason why the object is not send with the creation is that it gives a notification instead of the actual data - This permits a validation of the required permissions on the server side when client GETs the object(s).