-
Notifications
You must be signed in to change notification settings - Fork 79
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
backbone-relational, troubles with batch set if already have listeners that update same model #121
Comments
Thank you for reporting this. Is should be fixed in the next release |
seems issue still there. test for this issue is not fully correct.
in my example is important as well as using backbone.relational |
I've merged in the test. It looks like it passes when the atrributes are set in difference calls to set, but not in one call. Can I clarify something? Have you definitely determined that this is a Backbone-Relational issue (issue 485) so we can wait for a patch or do you need me to investigate? |
I'm pretty sure that PaulUithol/Backbone-relational#485 is a reason. knockback use changedAttributes to determine what is changed. But Backbone-Relational loose this info in some cases since they use event queue. For now, workaround is using setImmediate inside handler that change another model's property |
I have a model, and wrapped it to ViewModel
I update model with two options:
All works fine before I have another model that listen my model and change their properties in listener
in this case batch set to model like
did not update observable, and viewModel is out of date.
live sample
http://jsfiddle.net/MAZjQ/1/
The text was updated successfully, but these errors were encountered: