Skip to content

fix(material/datepicker): resolve typing issue when extending datepicker input in legacy app #25988

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

Conversation

crisbeto
Copy link
Member

In the switch to MDC we kept the reference to MatFormField in the datepicker input's constructor which now has a slightly different public API, causing a compilation error for apps that were passing in the legacy form field.

These changes replace the reference with an interface that contains only the common members that the datepicker cares about.

Fixes #25977.

…ker input in legacy app

In the switch to MDC we kept the reference to `MatFormField` in the datepicker input's constructor which now has a slightly different public API, causing a compilation error for apps that were passing in the legacy form field.

These changes replace the reference with an interface that contains only the common members that the datepicker cares about.

Fixes angular#25977.
@crisbeto crisbeto added 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 labels Nov 16, 2022
Copy link
Contributor

@zarend zarend 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 the action: merge The PR is ready for merge by the caretaker label Nov 16, 2022
@crisbeto crisbeto merged commit a38e08a into angular:main Nov 16, 2022
crisbeto added a commit that referenced this pull request Nov 16, 2022
…ker input in legacy app (#25988)

In the switch to MDC we kept the reference to `MatFormField` in the datepicker input's constructor which now has a slightly different public API, causing a compilation error for apps that were passing in the legacy form field.

These changes replace the reference with an interface that contains only the common members that the datepicker cares about.

Fixes #25977.

(cherry picked from commit a38e08a)
@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 Dec 17, 2022
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 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.

bug(datepicker): legacy datepicker module
2 participants