Skip to content

fix(material/radio): Apply tokens at mixin root #27864

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
Oct 1, 2023

Conversation

mmalerba
Copy link
Contributor

Applies radio tokens at the theme mixin's root selector (or html if the mixin is called with no selector). This makes it easier for users to override tokens without worrying about specificity.

@mmalerba mmalerba added the target: major This PR is targeted for the next major release label Sep 28, 2023
@mmalerba mmalerba requested a review from amysorto September 28, 2023 18:11
@mmalerba mmalerba force-pushed the radio-root branch 2 times, most recently from cef7de0 to e36b70c Compare September 28, 2023 23:56
Applies radio tokens at the theme mixin's root selector (or html if the mixin
is called with no selector). This makes it easier for users to override tokens
without worrying about specificity.
@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Oct 1, 2023
@mmalerba mmalerba merged commit dbd31de into angular:main Oct 1, 2023
@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 Nov 1, 2023
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 target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants