Skip to content

refactor(select,autocomplete): consolidate logic for scrolling options into view #9630

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
merged 1 commit into from
Feb 8, 2018

Conversation

crisbeto
Copy link
Member

Combines some duplicated logic for determining how to scroll an option into view into a single place so it's easier to maintain.

@crisbeto crisbeto requested a review from kara as a code owner January 26, 2018 20:55
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 26, 2018
* @param currentScrollPosition Current scroll position of the panel.
* @param panelHeight Height of the panel.
*/
static getScrollPosition(optionIndex: number, optionHeight: number, currentScrollPosition: number,
Copy link
Member

Choose a reason for hiding this comment

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

Could this be a standalone function rather than living on MatOption? Should this also be internal?

Copy link
Member Author

Choose a reason for hiding this comment

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

I went for consistency since the countGroupLabelsBeforeOption is also a static method. I'm fine with making it internal, but I can see it being useful if somebody is implementing a component that uses MatOption.

Copy link
Member

Choose a reason for hiding this comment

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

I'd rather keep the public API smaller and see if it comes up as a request first

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

…s into view

Combines some duplicated logic for determining how to scroll an option into view into a single place so it's easier to maintain.
@crisbeto crisbeto force-pushed the select-autocomplete-scroll-logic branch from 739ef05 to aab7426 Compare February 1, 2018 19:42
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 and removed pr: needs review labels Feb 1, 2018
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Feb 1, 2018
@mmalerba mmalerba merged commit b68d38c into angular:master Feb 8, 2018
mmalerba pushed a commit that referenced this pull request Feb 8, 2018
…s into view (#9630)

Combines some duplicated logic for determining how to scroll an option into view into a single place so it's easier to maintain.
tinayuangao pushed a commit that referenced this pull request Feb 9, 2018
…s into view (#9630)

Combines some duplicated logic for determining how to scroll an option into view into a single place so it's easier to maintain.
@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.

4 participants