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
I'm having and issue after my upgrade to ember 2.1, ember-data 2.1 and ember-data-sails 0.0.16/0.0.17. I'm using the SailsSocketAdapter and the ActiveModelSerializer. The sails backend has not changed (0.11.0). Any help is appreciated.
All standard requests are working as expected. Issues arise when a socket push message comes in. In my case for "comments".
When client A creates a comment, client B gets the websocket frame, but the comment is obviously not parsed as expected. With [email protected] and an old [email protected] the record was parsed and created, everything went fine (UI is updated, notification is created). In 0.0.16/0.0.17 with [email protected] not. Using the ember inspector I can see that the new model is not created.
In the receiving client I can see that the above frame is received. I can see that there are no errors on the console. I can see that there are no promises at all (i.e. no failing promises).
I've tried 0.0.13 - 0.0.15, but they won't work due to the ember-data changes from typeKey to modelName. 0.0.16 an 0.0.17 share the described behavior.
Am I missing something or might this be a bug?
Thanks, BR, toovy
The text was updated successfully, but these errors were encountered:
Hi huafu,
I'm having and issue after my upgrade to ember 2.1, ember-data 2.1 and ember-data-sails 0.0.16/0.0.17. I'm using the SailsSocketAdapter and the ActiveModelSerializer. The sails backend has not changed (0.11.0). Any help is appreciated.
All standard requests are working as expected. Issues arise when a socket push message comes in. In my case for "comments".
When client A creates a comment, client B gets the websocket frame, but the comment is obviously not parsed as expected. With [email protected] and an old [email protected] the record was parsed and created, everything went fine (UI is updated, notification is created). In 0.0.16/0.0.17 with [email protected] not. Using the ember inspector I can see that the new model is not created.
Here the frame that comes from sails:
In the receiving client I can see that the above frame is received. I can see that there are no errors on the console. I can see that there are no promises at all (i.e. no failing promises).
I've tried 0.0.13 - 0.0.15, but they won't work due to the ember-data changes from typeKey to modelName. 0.0.16 an 0.0.17 share the described behavior.
Am I missing something or might this be a bug?
Thanks, BR, toovy
The text was updated successfully, but these errors were encountered: