Skip to content

refactor(overlay): move connected position assertions into FlexibleConnectedPositionStrategy #10464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

crisbeto
Copy link
Member

Since the ConnectedPositionStrategy proxies everything to FlexibleConnectedPositionStrategy, these changes move the assertions that verify that the config looks correctly into the FlexibleConnectedPositionStrategy.

@crisbeto crisbeto requested a review from jelbourn as a code owner March 17, 2018 13:26
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 17, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release and removed pr: needs review labels Mar 29, 2018
@crisbeto crisbeto force-pushed the flexible-connected-position-assertions branch 2 times, most recently from 1f14b04 to c437e71 Compare April 5, 2018 21:15
@mmalerba
Copy link
Contributor

@crisbeto there seems to be some failing tests

@mmalerba mmalerba removed the action: merge The PR is ready for merge by the caretaker label Apr 19, 2018
@crisbeto crisbeto force-pushed the flexible-connected-position-assertions branch from c437e71 to 153f176 Compare April 20, 2018 12:23
@crisbeto
Copy link
Member Author

This is very odd. The errors definitely get thrown, but something ends up swallowing them.

@mmalerba
Copy link
Contributor

Could it be related to the new error handling behavior in rxjs 6?

https://github.com/ReactiveX/rxjs/blob/master/CHANGELOG.md#600-alpha1-2018-01-12

error handling: Unhandled errors are no longer caught and rethrown, rather they are caught and scheduled to be thrown, which causes them to be reported to window.onerror or process.on('error'), depending on the environment. Consequently, teardown after a synchronous, unhandled, error will no longer occur, as the teardown would not exist, and producer interference cannot occur

…nnectedPositionStrategy

Since the `ConnectedPositionStrategy` proxies everything to `FlexibleConnectedPositionStrategy`, these changes move the assertions that verify that the config looks correctly into the `FlexibleConnectedPositionStrategy`.
@crisbeto crisbeto force-pushed the flexible-connected-position-assertions branch from 153f176 to 005ecf2 Compare April 22, 2018 01:10
@crisbeto
Copy link
Member Author

Looks like that was the issue @mmalerba. I've pushed a fix.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Apr 22, 2018
@andrewseguin andrewseguin merged commit 2046b7a into angular:master Apr 23, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants