Skip to content

refactor: ensure typography mixins expect consistent arguments #18738

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

Currently we have a few components with typography mixins that do
not match the majority of other components. These components have
typography mixins where the $config is optional. We want to always
require a config (similar to how it's done in other components) to avoid
breaking changes in the future, and to have a consistent API.

Currently we have a few components with typography mixins that do
not match the majority of other components. These components have
typography mixins where the `$config` is optional. We want to
always require a config (similar to how it's done in other components)
to avoid breaking changes in the future, and to have a consistent
API.
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Mar 6, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 6, 2020
@mmalerba
Copy link
Contributor

mmalerba commented Mar 6, 2020

I think the idea was that not passing a config would default to using MDC's typography settings. Since we're now working on a separate plan for migrating Angular Material to use MDC's config format this change is probably ok

@mmalerba mmalerba added lgtm action: merge The PR is ready for merge by the caretaker labels Mar 6, 2020
@mmalerba mmalerba merged commit 3447891 into angular:master Mar 6, 2020
mmalerba pushed a commit that referenced this pull request Mar 6, 2020
Currently we have a few components with typography mixins that do
not match the majority of other components. These components have
typography mixins where the `$config` is optional. We want to
always require a config (similar to how it's done in other components)
to avoid breaking changes in the future, and to have a consistent
API.
@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 Apr 6, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants