Skip to content

Conversation

@hashchange
Copy link

Event handlers with standard names are run automatically if they exist, just like in Marionette. These standard names are

  • onSelect, onDeselect, onReselect (selectable model, single-select collection)
  • onSelectNone, onSelectSome, onSelectAll, onReselect (multi-select collection)

Based on my previous commits. Tests and documentation are included, as always.

hashchange and others added 20 commits December 30, 2013 16:00
deselectAll is more consistent with the rest of the API; selectNone is kept around for compatibility.
If a selectable model belongs to more than one selectable collection then only the initial collection will have it's select() method called.

Also, if a model is initially added to a non-selectable collection, and then later added to a selectable collection the 2nd collection will not have it's select() method called, and a error will be thrown as the initial collection will not have a select() method.
Backbone 1.0.0, Underscore 1.5.0. Using the listenTo and stopListening methods requires at least Backbone 0.9.9.
The extended model or collection is passed to the mixin as an argument now.
Events still need to be improved, those tests are failing.
Plus trivial changes in the tests to get rid of some warnings when committing.
…e in spec)

Previously, selectAll fired a select:all event even if all models had already
been selected beforehand. Similarly, deselectAll fired a select:none event
even if no model had been selected in the first place.

No-ops like this don't trigger an event any more.
Handlers named onSelect,  onDeselect etc are run without having to be
wired up first.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants