-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
master branch not saving hasMany relationship #287
Comments
Having the same issues, seems like updateRecords isnt serializing the records properly. Might be related to emberjs/data#3550 ? |
Thanks for the report, will do some testing and work out what's wrong. |
Thanks, Tim. Also, to confirm the error is not existent with Ember fire |
ok, I figured out what this is. It's ember-data JSONSerializer's i.e. when a |
Thanks for looking into it, Tim. is there something we should do in apps to mitigate this or is it likely to be solved by either ED or Emberfire in an upcoming release? |
I have a fix ready, just creating a breaking test to ensure this issue doesn't pop up again. |
Let me know if an updated master fixes your issue. Reopen this issue if you still have problems :) |
Looks like that fixed it. Thanks a lot! |
I have a hasMany relationship on a model:
I am creating stages and setting them on a feature. The stages array exists on the feature client-side. However, it is not persisted to the Firebase DB.
This is how I am saving the models:
Here is how the feature model appears in the Firebase DB:
One would expect an array of stages to be persisted to the feature model.
The stage model persists as expected:
Is there something obviously wrong here or could this be a bug on master branch?
The text was updated successfully, but these errors were encountered: