- From: Andrea Giammarchi <notifications@github.com>
- Date: Mon, 30 Mar 2015 05:18:42 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Monday, 30 March 2015 12:19:12 UTC
If you cancel you don't expect anything because you canceled. Going through `reject` what are you going to expect or why would even set at all that `.then` ? Agreed about the catch concern, which is why I went for a silent cancelation. If you cancel, whoever was interesting in the promise result will never be executed (but all Promises resolved regardless, no side-effect there, that's the goal of my design) Who canceled, could still do something with that promise, if needed, just to follow the pattern, not because it will exect a value. **However** in my initial design `.cancel(why)` was working as resolution for the promise, so that you can eventually cancel with a reason that will be passed to the next `.then` that is not in the canceled chain, but in the waiting one. Still not sure how much sense it makes. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/27#issuecomment-87654563
Received on Monday, 30 March 2015 12:19:12 UTC