-
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
Embedded hasMany not saving #354
Comments
it looks like you are doing everything correctly. I wonder if it's related to the inverse relationship. Can you remove duty's link back to the Otherwise, I'd like to get a minimal example so I can debug into it. |
It works! Great. But to be frank I need this inverse... Is there any workaround for this situation? |
Thanks for reporting back. It was a total guess... now I need to work out why this is the case... |
can you try the branch in #337 to see if using atomic saves + the ember-data EmbeddedRecordsMixin helps? |
Yes, it works! Thanks. |
Great, that branch will be EmberFire 2.0. I will make a release this week |
@tstirrat Great news if Emberfire 2.0 is coming this week! |
@tstirrat release on the way? :) |
There is more discussion on underlying ember-data bugs in #365, too |
@tstirrat Sorry, I hijacked this issue just to get info on a new release. :) My bad! Thanks for a great service! |
No problem 😸 |
Hi! I know it is a very old issue, but I'm experiencing the same problem. I tried to do what @jembezmamy did (b/c he said it worked) but in my case it didn't. I'm following the instructions in the guides, and my models are:
Any idea or suggestion? I use |
My hasMany relationship doesn't get saved when I use embedded records.
Then I run in console:
Then I get in firebase:
So as can you see, duty record is created and even assigned to the schedule, but schedule record has no duties assigned... Then, when I try to load this schedule in Ember, it also has no duties. Am I doing something wrong?
I use
ember 2.1.0
,ember-data 2.1.0
andember-fire 1.6.3
.The text was updated successfully, but these errors were encountered: