Skip to content

fix(material/schematics): handle input level in typography migration #25949

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
Nov 10, 2022

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Nov 10, 2022

Expands the logic in the MDC theming migration to be able to discern both keys and values of named Sass function parameters. The new logic is used to correctly migrate users away from the input typography level which doesn't have an equivalent in the new system.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround merge safe target: rc This PR is targeted for the next release-candidate labels Nov 10, 2022
@crisbeto crisbeto marked this pull request as ready for review November 10, 2022 12:34
Expands the logic in the MDC theming migration to be able to discern both keys and values of named Sass function parameters. The new logic is used to correctly migrate users away from the `input` typography levels which doesn't have an equivalent in the new system.
@crisbeto crisbeto self-assigned this Nov 10, 2022
@crisbeto crisbeto force-pushed the mdc-migration-input-level branch from 160ce63 to ca75155 Compare November 10, 2022 14:27
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 10, 2022
@crisbeto crisbeto merged commit 1e56524 into angular:main Nov 10, 2022
crisbeto added a commit that referenced this pull request Nov 10, 2022
…25949)

Expands the logic in the MDC theming migration to be able to discern both keys and values of named Sass function parameters. The new logic is used to correctly migrate users away from the `input` typography levels which doesn't have an equivalent in the new system.

(cherry picked from commit 1e56524)
@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 11, 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 P2 The issue is important to a large percentage of users, with a workaround target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants