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
BackboneJS >0.9.9 doesn't accept model.set(other_model) anymore #425
Comments
Great spot and annoying tests did not catch this change. Do you want to try patching or would you like someone else to take a quick look? (Happy either way) |
I'll need this fixed for ckan/ckan#1251. If someone else is able to do it before me, great! If not, I'll do it 👍 |
vitorbaptista
added a commit
to vitorbaptista/recline
that referenced
this issue
May 14, 2014
The problem is that Backbone >= 0.9.9 doesn't accept anymore updating models with: model.set(otherModel); That needs to be changed to: model.set(otherModel.attributes); Dataset.query() accepts both regular JS objects and Query models, so we need to check the parameter type to support both.
vitorbaptista
added a commit
to vitorbaptista/recline
that referenced
this issue
May 14, 2014
The problem is that Backbone >= 0.9.9 doesn't accept updating models with: model.set(otherModel); That needs to be changed to: model.set(otherModel.attributes); Dataset.query() accepts both regular JS objects and Query models, so we need to check the parameter type to support both.
rufuspollock
added a commit
that referenced
this issue
May 15, 2014
…one-0.9.9 [#425] Fix Dataset.query() when called with Query model
vitorbaptista
added a commit
to ckan/ckan
that referenced
this issue
May 15, 2014
This was fixed in datopian/datahub#425
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the changelog at http://backbonejs.org/:
We updated to
1.0.0
at 0801882 but forgot to do these changes, so there're a few places where Recline is failing silently. Usinggrep -rn "\.set(" src/
and filtering out valid uses, I got:Not all of these lines are errors, but we'll need to double check.
The text was updated successfully, but these errors were encountered: