Skip to content

feat(material-experimental/mdc-form-field): expose MAT_FORM_FIELD injection token #19277

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

Conversation

devversion
Copy link
Member

We recently added a new injection token called MAT_FORM_FIELD. This
token should allow form control implementers to inject the form-field
without having to bring in the actual MatFormField as a side-effect.

We should expose that token from the MDC form-field entry-point too,
as that will ease the migration. Also it would be unexpected if an
application switches to the MDC-based form field, but would still need
to import from the non-MDC form field entry-point.

…njection token

We recently added a new injection token called `MAT_FORM_FIELD`. This
token should allow form control implementers to inject the form-field
without having to bring in the actual `MatFormField` as a side-effect.

We should expose that token from the MDC form-field entry-point too,
as that will ease the migration. Also it would be unexpected if an
application switches to the MDC-based form field, but would still need
to import from the non-MDC form field entry-point.
@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels May 7, 2020
@devversion devversion requested a review from mmalerba as a code owner May 7, 2020 13:54
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 7, 2020
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels May 7, 2020
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 merged commit 5284a57 into angular:master May 7, 2020
jelbourn pushed a commit that referenced this pull request May 7, 2020
…njection token (#19277)

We recently added a new injection token called `MAT_FORM_FIELD`. This
token should allow form control implementers to inject the form-field
without having to bring in the actual `MatFormField` as a side-effect.

We should expose that token from the MDC form-field entry-point too,
as that will ease the migration. Also it would be unexpected if an
application switches to the MDC-based form field, but would still need
to import from the non-MDC form field entry-point.
@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 Jun 7, 2020
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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants