Skip to content

refactor(select): use mixin for disableRipple behavior #8847

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
Dec 8, 2017

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Dec 6, 2017

Switches mat-select to the common disableRipple mixin rather than re-implementing it.

Switches `mat-select` to the common `disableRipple` mixin rather than re-implementing it.
@crisbeto crisbeto requested a review from kara as a code owner December 6, 2017 20:42
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 6, 2017
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM. I assume CircleCI failed due to unrelated reasons.

@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Dec 6, 2017
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Dec 6, 2017
@mmalerba mmalerba merged commit 0c53312 into angular:master Dec 8, 2017
mmalerba pushed a commit that referenced this pull request Dec 8, 2017
Switches `mat-select` to the common `disableRipple` mixin rather than re-implementing it.
@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 7, 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