Skip to content
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

Fix unit-no-unknown false positives for unicode-range descriptors #6892

Conversation

romainmenke
Copy link
Member

Which issue, if any, is this issue related to?

Closes #6891

Is there anything in the PR that needs further explanation?

I forgot about <urange> productions when migrating rules to @csstools/css-tokenizer.

Parsing <urange> requires special handling and should only be done when inside a context that expects such values.

I've added a helper (isUnicodeRangeDescriptor) to make it easier for rules to skip @font-face { unicode-range: U+0100-024F; }

@changeset-bot
Copy link

changeset-bot bot commented Jun 4, 2023

🦋 Changeset detected

Latest commit: a7df1c1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
stylelint Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Member

@ybiquitous ybiquitous left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! LGTM 👍🏼

@romainmenke romainmenke merged commit 54b7376 into main Jun 5, 2023
14 checks passed
@romainmenke romainmenke deleted the fix-unit-no-unknown-false-positives-for-unicode-range-descriptors--sympathetic-geoffroys-tamarin-17b7c2b65a branch June 5, 2023 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Fix unit-no-unknown false positives for unicode-range descriptors
2 participants