feat(preset-mini)!: use getComponent for variant parameter #1704
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With
getComponent
helper, existingvariant-x
can more safely accept bracket value.This PR update the api of
variant-x
to usegetComponent
, in addition usingh.bracket
to process the passed parameter.Breaking changes:
combinators-x
variantsselector-x
scope-x
scope-x
no longer defaulted to class; x now must be a qualifying selectorpseudo-x
variantsgroup-x
,peer-x
,parent-x
,previous-x
media-x
variant can still use direct value for theme lookup, but missing key in the theme will no longer generate custom property valuemedia-x
syntax withsupport-x
syntaxlayer-x
anduno-layer-x
variants can still use direct value, in addition to bracket due to similarity with css@variant
container/parenth.bracket
so previous value of, ex.:variant-[uno_css]
, needs to be updated tovariant-[uno\_css]
to account forh.bracket
processingpseudo/label
experimental feature by tailwind. This may be changed down the line.Edit: added
scope-x
updateEdit 2: update label syntax