Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Document $q's notify behaviour #3755

Closed
wants to merge 2 commits into from

Conversation

colinfrei
Copy link
Contributor

Added basic documentation on $q's notify behaviour.

Closes #3341

*
* This method *returns a new promise* which is resolved or rejected via the return value of the
* `successCallback` or `errorCallback`.
* `successCallback`, `errorCallback`, or `notifyCallback`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible for a notifyCallback to resolve/reject a promise? From a quick inspection, their return values seem to be completely ignored here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I read you can't resolve or reject the promise from notifyCallback.
I'll doublecheck and add a note about that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think a note is necessary, just reverting this line should be enough.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah didn't push that commit yesterday. The same question came up in the original ticket, so in my eyes it warrants a quick note. See me latest change.

@vojtajina
Copy link
Contributor

Squashed, corrected the commit msg and merged as c65fcc0.
Thank you @colinfrei !

@vojtajina vojtajina closed this Aug 29, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document $q's notify/progress behaviour
3 participants