Each iterator on the repeated DOM element instead of container about ripple HOT 4 CLOSED

Can you post a code example? I think I know what you mean, just want to check

from ripple.

I first noticed this when trying to run the following:

customSMSTemplate = """
    <div class="SMSList">
      <div class="SMSList-add">
        <input type="text" ref="number" on-enter="{{ this.add }}" />
        <button on-click="{{ this.add }}">Add</button>
        <button on-click="{{ this.sort }}" hidden="{{ emptyList }}">Sort</button>
        <button on-click="{{ this.clear }}" hidden="{{ emptyList }}">Remove All</button>
      </div>
      <ul class="SMSList-list">
        <li each="{{items}}" >{{number}} <button on-click="{{ this.removeItem.bind(this, $index) }}">Remove</button></li>
         <li class="empty">Message when no data</li>
      </ul>
    </div>
"""

from ripple.

Mainly because it causes weird complications with having to worry about the order bindings are processed. That leads to a whole lot of weird mess that can usually be avoided by modifying the markup a little bit.

It could work if there was a limitation that you couldn't use other directives on the same element if you're using each. It's also a design of the plugin and not ripple, so we can change that without it affecting core :)

from ripple.

Sure, thanks for the clarification. As I've said, it was more curiosity than anything and indeed im more interested in explore how to control that kind of stuff with directives.

from ripple.