Skip to content

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 9, 2024

Includes a couple of changes (see individual commits) to ensure that we extract tokens correctly from the core-theme and that we correctly reflect tokens whose names overlap between different prefixes.

The tokens extraction script assumes that all the imported tokens will be used in the `overrides` mixin. That's true for all themes, except for `core` which only supports some of the mixins. These changes add a separate function that `core` can use to tell the tokens extraction script about which tokens are supported.
@crisbeto crisbeto added target: patch This PR is targeted for the next patch release merge: preserve commits When the PR is merged, a rebase and merge should be performed labels Oct 9, 2024
@crisbeto crisbeto requested a review from devversion October 9, 2024 08:58
@crisbeto crisbeto requested review from a team as code owners October 9, 2024 08:58
@crisbeto crisbeto requested review from mmalerba and removed request for a team October 9, 2024 08:58
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Oct 9, 2024
@crisbeto crisbeto removed the request for review from mmalerba October 9, 2024 09:26
We have many cases where we output a token with the same name under different prefixes from a theme. The way we were grouping the token data meant that this information was being lost.

These changes rework the data so each token has an array of `sources` that describe where the token is coming from.
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 9, 2024
@crisbeto crisbeto merged commit 7d54e2b into angular:main Oct 9, 2024
22 of 24 checks passed
@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 9, 2024
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 area: build & ci Related the build and CI infrastructure of the project merge: preserve commits When the PR is merged, a rebase and merge should be performed target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants