Skip to content

[v4] Only allow CSS variables in @theme#13125

Merged
RobinMalfait merged 5 commits intonextfrom
feat/error-on-unexpected-values-in-at-theme
Mar 7, 2024
Merged

[v4] Only allow CSS variables in @theme#13125
RobinMalfait merged 5 commits intonextfrom
feat/error-on-unexpected-values-in-at-theme

Conversation

@RobinMalfait
Copy link
Member

@RobinMalfait RobinMalfait commented Mar 7, 2024

This PR ensures that only CSS variables are allowed inside a @theme block.

If we detect something else (apart from comments and @keyframes), then we throw an error.

You can `Continue` its execution (the default behaviour), `Skip` walking
the current node, or `Stop` walking entirely.
There is no need to walk the `@theme` itself or to create a temporary
array here.
@RobinMalfait RobinMalfait force-pushed the feat/error-on-unexpected-values-in-at-theme branch from 048e678 to 37d1198 Compare March 7, 2024 11:34
@RobinMalfait RobinMalfait merged commit 324273c into next Mar 7, 2024
@RobinMalfait RobinMalfait deleted the feat/error-on-unexpected-values-in-at-theme branch March 7, 2024 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants