-
Notifications
You must be signed in to change notification settings - Fork 20
Expressions with tokenList, styleObject filters don't update dynamically #28
Comments
Thanks for tracking this down |
+1 |
…rties, due to PolymerExpression bugs: googlearchive/polymer-expressions#28 googlearchive/polymer-expressions#11
+1 |
|
+1 |
+1 |
+1 |
one possibility is addressing this at the filter level, by having some filters that work more like "array views" and are live. we could also observe the props of all the values ("classes" in above), but that adds more things we're Object.observing. Going to need to investigate what the perf implication of that is. |
Is this triple binding of polymer models <> DOM <> angular ng-models any help? |
Hi, In this codepen: http://codepen.io/anon/pen/azJeEL?editors=101 |
+1 |
1 similar comment
👍 |
This is a real problem. For example you cannot do the following: this.pages = ['over', 'there'];
<p>Sorry, but the page <code>{{pages | join('/')}}</code> doesn't exist.</p>
join: function(array, delimiter) {
return array.join(delimiter);
}, When the array changes the filter doesn't get updated resulting in an incorrect message. I would happily tackle a PR if someone can point me in the right direction. Any tips, @rafaelw or @jmesserly ? |
+1 |
👍 |
With an expression like:
The expression doesn't update when one of the values inside classes is updated. For example you might expect to be able to toggle the 'selected' class like this:
However, since the properties of
classes
aren't observed, the change isn't detected.Test case:
http://jsbin.com/qamat/12/edit
The Broken Switch button (which updates the property) doesn't trigger a change to the binding.
The Working Switch button (which clones the object) does trigger a change.
May be related to the issues mentioned in PR #23, of knowing which values to observe.
The text was updated successfully, but these errors were encountered: