Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

fix(bluebird): fix #1112, bluebird chained callback should return a Bluebird Promise #1114

Merged
merged 1 commit into from
Jul 27, 2018

Conversation

JiaLiPassion
Copy link
Collaborator

fix #1112.
The issue can be described as the following case.

new BluebirdPromise((resolve: any, reject: any) => {
      expect(Zone.current.name).toEqual('zone_A');
      resolve(1);
}).then((r: any) => {
      expect(r).toBe(1);
      expect(Zone.current.name).toEqual('zone_A');
      return Promise.resolve(2);
}).then((r: any) => {
      expect(r).toBe(2);
      expect(Zone.current.name).toEqual('zone_A');
});

So we should return a new bluebird promise in then callback.

@jrabbe
Copy link

jrabbe commented Jul 25, 2018

Changes LGTM, would be great to have this merged and released as soon as convenient, @mhevery. Thank you.

@mhevery mhevery merged commit 6ba3169 into angular:master Jul 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Patched bluebird does not provide data to promise chain
4 participants