Skip to content
This repository

Conflict between Marionette and Backbone.stickit #269

Closed
kevindente opened this Issue October 04, 2012 · 5 comments

3 participants

Kevin Dente Jarrod Overson Derick Bailey
Kevin Dente

The Backbone.stickit data binding library is configured by defining a "bindings" property on the view. Unfortunately, this conflicts with the .bindings property created by Marionette.

I've worked around it for now by using the overload of stickit that lets you pass in a binding configuration as a parameter instead of reading it from the view property. But it would be nice if they could co-exist more nicely.

Derick Bailey
Owner

+1

i'm not surprised this happened - it was just a matter of time, really. i'll see if i can get this figured out for the v0.11 release

Matthew DeLambo delambo referenced this issue in NYTimes/backbone.stickit October 06, 2012
Closed

bindings seem to be un-sticking #12

Derick Bailey
Owner

I'm having a hard time finding anything that uses a bindings setting in Marionette. am I looking for the wrong configuration / name?

Derick Bailey
Owner

I added Backbone.StickIt to my test suite for Marionette, in both the dev and master branch, and I don't see any conflicts. you sure this is a conflict with Marionette?

Kevin Dente

It's actually with BindTo (I'm still on 0.9.3). In the bindTo function, "this.bindings.push". Maybe with the BindTo extraction this isn't a problem any more.

Jarrod Overson jsoverson closed this October 06, 2012
Jarrod Overson
Owner

Yeah, this is no longer an issue since BindTo was renamed and refactored to EventBinder. Bindings are stored in this._eventBindings now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.