We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
3.0.0-beta.9
#406
Attempts to work with a changeset for an ember data model with more than one attr fails when it tries to commit the changes.
It appears to be a bug somewhere inside buildPathToValue. Given a simple model like {foo: 1, bar: 2} it will attempt to set a value at foo.bar.
{foo: 1, bar: 2}
foo.bar
Saving models with more than one attr should not throw errors.
Models should save. ;)
The text was updated successfully, but these errors were encountered:
It looks like it boils down to unexpected behavior when checking foo.hasOwnProperty(key).
foo.hasOwnProperty(key)
Sorry, something went wrong.
I was able to fix it, but I'm not sure it's the ideal solution: 6170b40
Edit: Spoke to soon. Adding a relationship to that model will result in the same kind of bug.
PR now has fixes for all the scenarios I found.
Fixed by #406
No branches or pull requests
Version
3.0.0-beta.9
Test Case
#406
Steps to reproduce
Attempts to work with a changeset for an ember data model with more than one attr fails when it tries to commit the changes.
It appears to be a bug somewhere inside buildPathToValue. Given a simple model like
{foo: 1, bar: 2}
it will attempt to set a value atfoo.bar
.Expected Behavior
Saving models with more than one attr should not throw errors.
Actual Behavior
Models should save. ;)
The text was updated successfully, but these errors were encountered: