Skip to content
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

DS.Errors#add/remove/clear should not be marked as deprecated? #4694

Closed
HeroicEric opened this issue Dec 5, 2016 · 2 comments
Closed

DS.Errors#add/remove/clear should not be marked as deprecated? #4694

HeroicEric opened this issue Dec 5, 2016 · 2 comments

Comments

@HeroicEric
Copy link
Member

HeroicEric commented Dec 5, 2016

As a result of #3853, DS.Errors#add, DS.Errors#remove, and DS.Errors#clear were marked as deprecated but no deprecation was added to the functions. Instead, a warning was added to the functions to make sure the behavior was clear.

I think we need to either

  • add deprecations to these functions
  • remove the @deprecated tags
@runspired
Copy link
Contributor

runspired commented Apr 19, 2018

We discussed this recently and I believe we do want to move to deprecate, possibly even go all the way to assertion.

After reading through the code it appears as though the warning was meant to be a partial behavior deprecation for something we intended to change in 3.0; however, we never changed it in 3.0. We partially removed the deprecated Evented functionality in 3.4 but looking back I think we didn't quite finish the job, will submit a follow up PR and clean this up.

@runspired
Copy link
Contributor

Closing as we decided to not pursue a deprecation at this time. The RecordData Errors RFC will provide an alternative path to a future without this class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants