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
should @computed('attr.something.@each.foo') provide attr.something? #20
Comments
We should just pass in the portion prior to the |
my thoughts exactly +1 |
I ran into this behaviour just yesterday, and frankly I was rather surprised to discover that I wasn't getting the value passed through to my computed function that I had specified as my dependent key. The behaviour exhibited was non-obvious to me and unexpected. Yes, I do realise that the behaviour from this issue is as has been documented, but I had skipped past that part of the documentation before. My presumption was that by specifying it as the key I'd get passed Had I wanted to work with |
I think this is now more of a concern with kellyselden/ember-macro-helpers, as this lib now just wraps that one as a decorator |
example:
thoughts?
The text was updated successfully, but these errors were encountered: