You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently ran into trouble with value$= data bindings in iron-list, I wasn't able to replicate that exact issue but it appears as if iron-list isn't observing array change notification declared using computed bindings or observers. I've setup examples of both and if you try to delete a record (which utilizes this.splice), iron-list will not update.
The text was updated successfully, but these errors were encountered:
@indolering this one does work: http://jsbin.com/qasahupapi/1/edit?html,output iron-list currently doesn't support array filtering in the same way dom-repeat does. That feature is in the backlog and we do want to fully support it. It's just a matter of priorities.
Things to keep in mind:
Observe to items.* to get notification for splices.
If the array is mutated without using the Polymer's mutation API, the only way to reflect the changes is to create a copy of the array. That's why you see the array.slice.
Also, this a temporary solution. Generally speaking calling array.slice is just hack here.
I recently ran into trouble with
value$=
data bindings in iron-list, I wasn't able to replicate that exact issue but it appears as if iron-list isn't observing array change notification declared using computed bindings or observers. I've setup examples of both and if you try to delete a record (which utilizesthis.splice
), iron-list will not update.The text was updated successfully, but these errors were encountered: