Skip to content

fix(form-field): annotate base class with Directive for Ivy #17457

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
Oct 21, 2019

Conversation

crisbeto
Copy link
Member

This is a resubmit of #17022, excluding the portal changes. It marks the MatFormFieldControl as a directive because it's being extended by other directives which can cause errors under Ivy.

@crisbeto crisbeto added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: major This PR is targeted for the next major release labels Oct 21, 2019
@crisbeto crisbeto added this to the 9.0.0 milestone Oct 21, 2019
@crisbeto crisbeto requested a review from mmalerba as a code owner October 21, 2019 19:50
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 21, 2019
This is a resubmit of angular#17022, excluding the portal changes. It marks the `MatFormFieldControl` as a directive because it's being extended by other directives which can cause errors under Ivy.
@crisbeto crisbeto force-pushed the form-field-control-directive branch from df1ab95 to cc28173 Compare October 21, 2019 20:01
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 21, 2019
@mmalerba mmalerba merged commit 4663d8f into angular:master Oct 21, 2019
@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 Nov 21, 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 P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful 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