-
-
Notifications
You must be signed in to change notification settings - Fork 8
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/ordered-set does not avoid deprecation warnings #19
Comments
👍
Yes, that was exactly the goal. 🤔
Yes, please 🙏 . |
I think we don't want a global flag though -- anybody who is trying to use Ember.OrderedSet directly should still see a deprecation until they switch to using it via |
@ef4 - Ahh, good point. In that case, I think we need to add the following to my steps above:
What do you think? |
Yup, @savvymas is already embarking in that direction. |
My understanding of this addon is that people should switch to it to avoid deprecation warnings from the built-in ordered-set inside Ember. Which is what ember-data is doing here.
But using ember-data 3.1.1 (which is importing from
@ember/ordered-set
) with ember-canary we still get the deprecation. Presumably because @ember/ordered-set falls back to the built-in implementation in an effort not to bloat code size.Do you want PRs to ember and ordered-set to create a deprecation-free private path?
cc @savvymas
The text was updated successfully, but these errors were encountered: