This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
$q.when should be deprecated #13709
Labels
Milestone
Comments
We are not really removing features in the 1.x branch, so deprecation is a bit meaningless, but we can update the docs to recommend using $q.resolve instead of $q.when. |
The docs currently state: resolve(value, [successCallback], [errorCallback], [progressCallback]); Alias of when to maintain naming consistency with ES6. This seems to be a reversal of what's currently recommended? https://docs.angularjs.org/api/ng/service/$q |
The |
If someone wants to change all instances of |
ellimist
pushed a commit
to ellimist/angular.js
that referenced
this issue
Mar 15, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since Angular 1.4.1 there is a new (more consistent) method $q.resolve that does the exact same thing. I think it might be a good idea to deprecate the $q.when method and remove it in a future release.
The text was updated successfully, but these errors were encountered: