-
Notifications
You must be signed in to change notification settings - Fork 41
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
Incoming private API breakage #159
Comments
@ef4 any idea how we can figure out if |
It seems that this code just warns and gives up when it can't write to attrributeBindings, so perhaps you can just try to |
guess I'll wait until this code actually breaks in canary and then we'll see how to fix/work around it |
Yeah, that's reasonable. The relevant RFC is emberjs/rfcs#281 |
This issue is causing a test to fail in #172 |
indeed, I'm just surprised that it works without issues in one of our apps that is running 3.0 🤔 |
It will only break if you happen to have attributesBindings as a computed property. It's not a common thing to do. |
Accessing anything on a
ComputedProperty
instance is private API and is likely to break in the future (possibly the very soon future). This addon is accessingisDescriptor
:https://github.com/simplabs/ember-test-selectors/blob/master/addon/utils/bind-data-test-attributes.js#L30
The tl;dr is that everybody wants to make
Ember.get
optional and just use real ES5 getters for computed properties. As soon as we do that,component.attributeBindings
will stop giving you aComputedProperty
instance with anisDescriptor
, and would always return the value directly, even when it is implemented as computed property.The text was updated successfully, but these errors were encountered: