-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Annotated attribute binding issues #1874
Comments
As you noted in #1877 (comment), what you are seeing is a result of Polymer's rule to not call observers/computing functions with undefined dependencies (discussed in docs here), which has both performance and ergonomic benefits, but has this side-effect of slightly unintuitive results when structured data may have optional properties that lead to In this case, I'd recommend using a wildcard argument, which guarantees the function is called for each change to the base object and sub-properties thereof: We'll consider improvements to this API on #1877, so we'll go ahead and close this issue. |
Thanks for the help |
I'm having trouble w/ a callback not executing whenever an annotated attribute binding uses a function which takes multiple args and one of them is undefined.
If I limit the number of arguments to 1, everything seems to work as expected.
Here's a plnkr
http://plnkr.co/edit/FlN0SJmmjgyEJRlkRE0w?p=preview
Note: That example uses
dom-repeat
, but I'm getting the same result when using a standalone object outside of any repeater.The text was updated successfully, but these errors were encountered: