Fix usage of special-character prefixes #8772
Merged
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.
This was a regression in v3.1 with the rewritten candidate extractor. Now we explicitly add the prefix to the regex to be matched so it could theoretically be anything. In practice there are some characters that won't work for internal reasons.
We still have to pick up candidates for non-prefixed things because the user can write their own class names in an
@layer
so the prefix is optional but it will now pick it up when necessary.Fixes #8702