brian-mann/backbone.chooser

Easily track chosen models in collections

backbone.chooser's Issues

Move model chosen flag to internal property.

Because Backbone.Chooser uses a model attribute to store the chosen state, when saving the model, the chosen flag is also sent in the request.

In my scenario, the chosen field is not part of the original data that populated the model. My API doesn't recognize it in the schema, which causes an error.

Would it be possible to set the flag on a "private" property for the model?

bug in collection.unchoose(models, [options])

Seems to only work if all the passed models are chosen. As soon as the for loop hits an unchosen model it breaks the loop and the effect is the not all passed models get unchosen.

Possibly not a bug, but should be in readme that it will only accept chosen models.

"collection:unchose:one" event should be fired when you choose a new model in SingleChooser

Right now in SingleChooser when one calls collection.choose(model), the previously selected models are removed from the @Chosen array, but the "collection:unchose:one" event is not fired for them. And if the BackboneChooser is not defined on the model then even the "model:unchosen" event is not fired. One really needs to keep a track of the unchosen models as well.

Move MultiChooser#chooseNone to BaseChooser#chooseNone.

Seeking a way to clear selection at the collection level (single and multiple). There is chooseNone in the MultiChooser, but an option doesn't exist for the SingleChooser.

Thoughts?

doc typo: toggleChosen() => toggleChoose();

SingleChooser - add the ability to unchoose a selected model

It would be nice to be able to unchoose chosen model in SingleChooser, because right now one has to:

var maybeModel = collection.getFirstChosen(); 
if (maybeModel) {
    collection.unchoose(maybeModel);
}

Maybe like with MultiChooser. getChosen() and MultiChooser. getFirstChosen(), the MultiChooser. chooseNone() can be available on SingleChooser.

Thank You

Unit Tests

Hey Brian,

I'm almost done writing unit tests for this behavior in our implementation, maybe it'd be a better idea if we unit-test the plugin though? Would you be interested in that?

Thanks,

• Steven