You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v7.1.1, Jest-styled-components replaced css dependency to @adobe/css-tools. There is a bug in @adobe/css-tools where its parses chained selectors incorrectly. Chained selectors with psuedo-states are parsed incorrectly.
The text was updated successfully, but these errors were encountered:
endpoint-vtsang
changed the title
Chained selectors with pseudo-state filters are parsed incorrectly in v7.1.1
[Bug] Chained selectors with pseudo-state filters are parsed incorrectly in v7.1.1
Oct 6, 2022
Problem
In v7.1.1, Jest-styled-components replaced
css
dependency to@adobe/css-tools
. There is a bug in@adobe/css-tools
where its parses chained selectors incorrectly. Chained selectors with psuedo-states are parsed incorrectly.For example
Before the update,
css
would parse the rule as two selectorsAfter the update,
@adobe/css-tools
would parse the rule as one selectorThis would result in an error where it can't find the selector with
toHaveStyleRule()
How to debug
In
node_modules/jest-styled-components/src/toHaveStyleRule.js
, add a console.log ingetRules()
Link to barebone repo
The text was updated successfully, but these errors were encountered: