-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Ember uses deprecated features #17964
Comments
Listeners are inherited lazily, so there's no way for us to know ahead of time that they will cause a deprecation. When we first notify a property that causes the listener to fire, we collapse the inheritance tree and encounter the issue, throwing the deprecation message. You should look through your code to see where you are doing |
@pzuraq It is not my code:
|
If that's the deprecation message you are seeing, I believe this is a different listener that is being triggered by that observer. Those observers are only ever added to instances, the If you still need to debug this, please put a breakpoint at the location of the deprecation and log the function, so we can be sure. |
It's an ember issue, replicated with this command: Ember.ObjectProxy.extend({ a: function () {}.observes('b') }).create() |
That's not supported anymore, and trying that out locally I get a different deprecation:
I don't get the deprecation you're describing. |
My mistake actually, I was able to reproduce this after switching to an older version of Ember. You are correct, this is a bug, will submit a fix shortly. Sorry again for the confusion, it's been a long week! |
I'm working though upgrading our app from 3.4 LTS to 3.8 LTS. I've removed 7500+ of the We're using Will this fix be backported, so that 3.8 LTS users get the benefit? Thanks! |
|
Perfect, down to 0 warnings (of that type, at least). Thanks! |
The events.inherited-function-listeners deprecation triggers from within ember itself.
The triggered method:
ember.js/packages/@ember/-internals/runtime/lib/mixins/-proxy.js
Lines 21 to 27 in a7d861b
The text was updated successfully, but these errors were encountered: