Skip to content
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

fix(autocomplete): not implementing setDisabledState from ControlValueAccessor #8746

Merged

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Nov 30, 2017

Fixes plain inputs (without a matInput) that have a formControl and an autocomplete attached not being disabled via FormControl.disable. The issue was due to the MatAutocompleteTrigger not implementing the setDisableState. The current implementation is in line with the approach in the DefaultValueAccessor.

Fixes #8735.

@crisbeto crisbeto requested a review from kara as a code owner November 30, 2017 20:42
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 30, 2017
@crisbeto crisbeto force-pushed the 8735/autocomplete-disabled-state branch from 71a471c to ebcea44 Compare December 2, 2017 10:21
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
Copy link
Member

jelbourn commented Dec 5, 2017

Also needs rebase

…eAccessor

Fixes plain inputs (without a `matInput`) that has a `formControl` and an autocomplete attached not being disabled via `FormControl.disable`. The issue was due to the `MatAutocompleteTrigger` not implementing the `setDisableState`. The current implementation is in line with the approach in the `DefaultValueAccessor`.

Fixes angular#8735.
@crisbeto crisbeto force-pushed the 8735/autocomplete-disabled-state branch from ebcea44 to 93bda3c Compare December 6, 2017 19:00
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release target: patch This PR is targeted for the next patch release and removed pr: needs rebase target: minor This PR is targeted for the next minor release labels Dec 6, 2017
@andrewseguin andrewseguin merged commit 92bc503 into angular:master Dec 13, 2017
andrewseguin pushed a commit to andrewseguin/components that referenced this pull request Dec 19, 2017
…eAccessor (angular#8746)

Fixes plain inputs (without a `matInput`) that has a `formControl` and an autocomplete attached not being disabled via `FormControl.disable`. The issue was due to the `MatAutocompleteTrigger` not implementing the `setDisableState`. The current implementation is in line with the approach in the `DefaultValueAccessor`.

Fixes angular#8735.
@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.

Can not disable custom MatFormFieldControl with FormControl with mat-autocomplete
4 participants