Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

WIP - feat($route): wait for resolves #15587

Closed
wants to merge 2 commits into from

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Jan 9, 2017

Based on #14159. Just triggering CI.

Protractor users were having a problem where if they had asynchonous code in a route.resolve
variable, Protractor was not waiting for that code to complete before continuing. See
angular/protractor#789 (comment) for details

Also enhanced ngMock to wait for pending requests before calling callbacks from
`$browser.notifyWhenNoOutstandingRequests`

Potentially breaking change if someone was relying on route.resolve not blocking
`$browser.notifyWhenNoOutstandingRequests`
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

1 similar comment
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@gkalpak gkalpak force-pushed the feat-route-wait-for-resolves branch 2 times, most recently from b2bfbd9 to 8503bc3 Compare January 9, 2017 19:40
@gkalpak gkalpak force-pushed the feat-route-wait-for-resolves branch from 8503bc3 to e7cea3d Compare January 9, 2017 20:15
Copy link
Contributor

@sjelin sjelin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm cool with your version or my version. But if you want to stick with this PR, you'll have to add unit tests for resolveRedirectTo

expect(callback).toHaveBeenCalled();
});
});
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs test for resolveRedirectTo

loadFixture('ng-route-promise');
});

it('should wait for promises in resolve blocks', function() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

description needs to be updated

@gkalpak
Copy link
Member Author

gkalpak commented Jan 10, 2017

I'm cool with your version or my version.

I've just opened this one to run some tests on CI. Let's go with yours.

@gkalpak gkalpak closed this Jan 10, 2017
@gkalpak gkalpak deleted the feat-route-wait-for-resolves branch January 10, 2017 13:38
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.

3 participants