Store bindings in each view, instead of a globally shared array #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
delambo
added a commit
that referenced
this pull request
Sep 25, 2012
Store bindings in each view, instead of a globally shared array
|
@KidkArolis Thanks! I think this cleans up the multi-view use-case that I hacked into issue #4. |
delambo
added a commit
that referenced
this pull request
Sep 25, 2012
delambo
added a commit
that referenced
this pull request
Sep 25, 2012
|
@KidkArolis Heads up - I just committed an additional fix for this to master (the case when multiple models are initialized by calling stickit again). |
|
Good stuff :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the _modelBindings array was shared among all views, which means when one view is destroyed, all of the bindings in all views are lost.
Should I provide tests reproducing the problem?