Skip to content

feat(overlay): add the ability to set the default offsets on FlexibleConnectedPositionStrategy #10555

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

Ports over the functionality that we used to have on the ConnectedPositionStrategy where consumers can set a default offset on the position strategy itself, to which it'll fall back if a ConnectedPosition doesn't have an offset. This helps avoid repetition in the cases where the consumer wants to have the same offset on all positions.

@crisbeto crisbeto requested a review from jelbourn as a code owner March 24, 2018 17:10
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 24, 2018
* Sets the default offset for the overlay's connection point on the x-axis.
* @param offset New offset in the X axis.
*/
withOffsetX(offset: number): this {
Copy link
Member

Choose a reason for hiding this comment

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

Can we call these withDefaultOffsetX, withDefaultOffsetY? That will make it more clear that the offsets aren't additive.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure, done.

@crisbeto crisbeto force-pushed the flexible-connected-position-offset branch from a33cd33 to 946c117 Compare March 26, 2018 17:24
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: major This PR is targeted for the next major release and removed pr: needs review labels Mar 26, 2018
@josephperrott
Copy link
Member

@crisbeto Looks like there are a couple errors, can you rebase and push again?

…ConnectedPositionStrategy

Ports over the functionality that we used to have on the `ConnectedPositionStrategy` where consumers can set a default offset on the position strategy itself, to which it'll fall back if a `ConnectedPosition` doesn't have an offset. This helps avoid repetition in the cases where the consumer wants to have the same offset on all positions.
@crisbeto crisbeto force-pushed the flexible-connected-position-offset branch from 946c117 to 2a06373 Compare March 28, 2018 19:16
@crisbeto
Copy link
Member Author

Those seemed to be coming from master @josephperrott (e.g. the issue with the Browserstack key). I've rebased the PR.

@josephperrott josephperrott merged commit bcff93e into angular:master Mar 30, 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: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants