Request: deferred.isUnresolved()

[giskard22]

Sometimes I want to see if a Deferred is still pending. I have to do:

if (def.isResolved() || def.isRejected()) ...

It would be easier to just check def.isUnresolved().

[john]

Let's consider this for 1.7.

[jaubourg]

I'd vote for isPending()

[john]

Nominating ticket for 1.7 discussion.

[rwaldron]

+1,

[jaubourg]

+1, when a deferred is rejected then it is unresolved. Better call this isPending or something.

[timmywil]

+1,

[dmethvin]

+1, Definitely.

[john]

+0, Don't have strong feelings regarding this.

[addyosmani]

+1

[ajpiano]

+1, and we should use the name isUnresolved to maintain the dichotomy

[Jethro Larson]

An other possibility: ! def.isResolved()

[jaubourg]

It's called isProgressing and is in master.

Related commit:  https://github.com/jquery/jquery/commit/a588336a6dcc6f29e870e8fcdd243f96bec5e833

[dmethvin]

It may be subtle, but I think .isProgressing() has a different implication than .isUnresolved(). The former implies some sort of progress is still being made, whereas the latter just says it's not yet done.

[jaubourg]

Replying to dmethvin:

It may be subtle, but I think .isProgressing() has a different implication than .isUnresolved(). The former implies some sort of progress is still being made, whereas the latter just says it's not yet done.

While .isProgressing() returns true, you can still notify progress (for progress callbacks). I'm just trying to be consistant with the rest of the API:

• isResolved(): .resolve() has been called
• isRejected(): .reject() has been called
• isProgressing(): progress callback can be trigerred

-ed for one-time actions, -ing for repeatable callbacks with an emphase on the callback type.

I'm strictly against isUnresolved, seeing as it is completely misleading (shouldn't it return true when the deferred is rejected?).

[dmethvin]

Clarifying: The actual resolution in 1.7 was to add a .state to the Deferred. The .isResolved() and .isRejected() methods are deprecated and will be removed in 1.8.