You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, every await*() method cancels any remaining promises. This is debatable, but IMHO the "await" implies that we either wait for the promises to settle or will never care about their (possible) future results.
Arguably, another use case would be "checking" whether a promises settles within a given time frame. I'd like to put this out here to see if anybody happens to have any thoughts and/or actual use cases.
Activity
clue commentedon Jul 2, 2015
I think these are actually two independent use cases that should be clearly separated.
As such, I'd vote against a boolean flag (boolean trap?) and vote for two distinct methods similar to this:
The default should probably to not cancel any promises, as this is the default promise behavior (e.g.
Promise\all()). (Warning, BC break ahead).Also refs #5.
clue commentedon Jul 11, 2015
I'll postpone this ticket until we find a valid use case for non-cancellation behavior.
This might be relevant again once #14 is being implemented: Should we cancel every promise once we run into a timeout?
@ALL: If you happen to have a use case, please update this ticket.
clue commentedon Mar 9, 2016
Given we have yet to find a use-case for this, I'll close this for now. Feel free to comment and I'm happy to reconsider.