Open yinhm opened 10 years ago
It's disappoints me too. I fix it with
JSON.stringify(data, function(key, value) { return key === 'deferred' ? undefined : value; }));
Also when we send JSON does the data have to be under a message key? Just wondering why not send the data with the same JSON supplied as an argument to the send method? (on the server I have to do $message->message->propertySetInSendJSON).
Thanks.
Yes this is definitely a bug, @globin 's PR fixes this for me.
+1 for this bug
Seems like its still open!
I found ngSocket send
"deferred":{"promise":{}}
as part of json message when I was migrating from another websocket library. See: angular/ngSocket/blob/master/src/ngSocket.js#L136I don't see the reason behind this, I have monkey patched it to:
to make it compatible with my server code.
I think ngSocket should not make any assumption of server implementation. So my question is: can we let user define what it should send?