1) What version of bluebird is the issue happening on?
3.7.2
2) What platform and version? (For example Node.js 0.12 or Google Chrome 32)
Node.js 10.x
3) Did this issue happen with earlier version of bluebird?
Unknown
(Write description of your issue here, stack traces from errors and code that reproduces the issue are helpful)
The docs on cancellation state:
As an optimization, the cancellation signal propagates upwards the promise chain so that an ongoing operation e.g. network request can be aborted.
There seems to be no way to prevent the propagation- that is, if a child promise is cancelled, there is no way for the parent calling promise to continue.
This can be restrictive.
Perhaps there could be a function added like noCancelPropagation() that would cause only the initial promise to be cancelled.
You can create and keep a second fork of that promise (using then) and the cancellation should be unable to propagate past that point unless the fork also cancels
Please answer the questions the best you can:
1) What version of bluebird is the issue happening on?
3.7.2
2) What platform and version? (For example Node.js 0.12 or Google Chrome 32)
Node.js 10.x
3) Did this issue happen with earlier version of bluebird?
Unknown
(Write description of your issue here, stack traces from errors and code that reproduces the issue are helpful)
The docs on cancellation state:
There seems to be no way to prevent the propagation- that is, if a child promise is cancelled, there is no way for the parent calling promise to continue.
This can be restrictive.
Perhaps there could be a function added like
noCancelPropagation()
that would cause only the initial promise to be cancelled.