This repository was archived by the owner on Oct 2, 2019. It is now read-only.
on-remove and on-select should fire AFTER addition/removal of the item #501
Conversation
This file contains hidden or 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
|
Thanks! Pending review, you can assume this will merge and proceed accordingly. |
|
Actually, @gotenxds, scope is pretty small, I'll merge now and then wait a bit for a version bump to release this. But first I need you to rebase. Thanks! |
brianfeister
pushed a commit
that referenced
this pull request
Dec 14, 2014
on-remove and on-select should fire AFTER addition/removal of the item
|
Released in v0.9.6 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixed the issue where on-remove and on-select would fire before the scope was updated.