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(material/form-field): undeprecated legacy and standard appearances #18144

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

mmalerba
Copy link
Contributor

@mmalerba mmalerba commented Jan 9, 2020

There are a few bugs to address with outline and fill styles before we
can deprecate these.

There are a few bugs to address with outline and fill styles before we
can deprecate these.
@mmalerba mmalerba added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful pr: merge safe target: patch This PR is targeted for the next patch release labels Jan 9, 2020
@mmalerba mmalerba added this to the 9.0.0 milestone Jan 9, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 9, 2020
Copy link
Member

@Splaktar Splaktar left a comment

Choose a reason for hiding this comment

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

LGTM

@Splaktar
Copy link
Member

Splaktar commented Jan 9, 2020

Reverts PR #17961.

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.

I think we should write down what the plan for the MDC version is. Surely, it will be on the list to ensure that the alignment issues are solved, but since this will shift the deprecation, the MDC form-field either needs to wait until we can make this breaking change, or we need to provide a standard/legacy implementation?

@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 12, 2020
@mmalerba mmalerba added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Jan 13, 2020
@mmalerba
Copy link
Contributor Author

CARETAKER NOTE: cherrypick into 9.0.x branch

@andrewseguin andrewseguin merged commit d550e4e into angular:master Jan 15, 2020
andrewseguin pushed a commit that referenced this pull request Jan 15, 2020
#18144)

There are a few bugs to address with outline and fill styles before we
can deprecate these.
yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
angular#18144)

There are a few bugs to address with outline and fill styles before we
can deprecate these.
@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 Feb 15, 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 merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants