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 custom property sets #5307

Merged
merged 1 commit into from
May 16, 2021
Merged

Fix custom property sets #5307

merged 1 commit into from
May 16, 2021

Conversation

jeddy3
Copy link
Member

@jeddy3 jeddy3 commented May 15, 2021

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

#5304

Is there anything in the PR that needs further explanation?

PostCSS used to parse custom property sets as rule nodes, and we added code to some of our built-in rules to handle this. PostCSS now parsers them as decl nodes:

{
  "prop": "--foo",
  "value": "{ color: red; }"
}

The spec is abandoned and we should no longer attempt to support it.

This pull request remove any special handling of custom property sets.

It fixes 4 more tests. Leaving only the disable-ranges one.

@jeddy3 jeddy3 merged commit f835323 into update-to-postcss-8 May 16, 2021
@jeddy3 jeddy3 deleted the fix-custom-prop-set branch May 16, 2021 08:20
jeddy3 added a commit that referenced this pull request May 20, 2021
jeddy3 added a commit that referenced this pull request Jun 7, 2021
* Update postcss dependencies

* Fix invalid position for attribute selector (#5305)

* Fix custom property sets (#5307)

* Update dependencies

* Fix types issues after PostCSS update (#5346)

* Migrate stylelint PostCSS plugin to Visitors API (#5353)

Co-authored-by: Aleks Hudochenkov <aleks@hudochenkov.com>
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.

None yet

2 participants