if one binding dom element doesn't exist, nothing renders about backbone.stickit

[andriijas]

userBindings:
  '#username': 'username'

render: ->
   if loggedin
      @stickit @model, userBindings

in js:

  userBindings: {
    '#username': 'username'
  },
  render: function() {
    if (loggedin) {
       this.stickit(this.model, userBindings);
    }
  }

[delambo]

I second @andriijas' approach - create two bindings objects for the different states.

[malkomalko]

on second thought here though, I wonder why the whole thing should bork if one field in your bindings map doesn't exist? I almost feel like it should just ignore bindings that don't exist instead of stopping the train. that would decrease the need for creating logic to handle multiple bindings as in the scenario described... no?

[delambo]

I'm not quite sure if I understand your problem. I setup the following fiddle with a selector to an element that doesn't exist and it seems to work fine:

http://jsfiddle.net/px6UP/6/

Can you modify this fiddle to show me what you are seeing?

[sllanes]

I ran into this issue recently. The problem is that I was using lodash and not underscore. In the stickit function there is an "each" loop that returns false if the selector does not find an element. It appears lodash's "each" does not support early breaking of the loop while underscore does. I switched to underscore to fix the issue. Is the "return false" intended to be an early break or is it meant to abandon applying the bindings?

I did read that underscore should not support early breaking in each loops but it seems it does in version 1.4.4: jashkenas/underscore#960.

And lodash says it does not support early breaking as well: lodash/lodash#99.

That leaves me a little confused but the switch to underscore does seem to address my problem.

[delambo]

Removed false from that return statement on master.