Fix CSS-in-JS problems #4574
Description
We have a bunch of CSS-in-JS related problems. I've gathered them here:
- #4119 — Fix autofix for nested tagged template literals
- #4490 — Fix autofix erroneous changes for float property
- #4560 — Fix autofix transforming media queries when no errors
- #4401 — Fix 'cannot parse selector' error for nested HTML elements
- #4247 — Support Vue-emotion syntax
- #4635 — Fix false positives for "always" option in declaration-empty-line-before
- #4655 — Fix false positives for single value within template literal
- #4662 — Fix autofix for variable name matching property name
- #4684 — Fix false positives for rule-set interpolation in selector-max-empty-lines
- #4706 — Fix false positives when importing from module with
cssin name - #4761 — Fix false negatives for decorators
- #4732 — Fix false negatives for TypeScript files and Babel config
- #4713 — Fix false positives for negation within interpolation in declaration-bang-space-before
- #4919 — Fix false positives for jQuery CSS function in value-keyword-case
- #5185 — Fix false positives for JS variables in value-keyword-case
- #5235 — Fix false positives for attrs in property-no-unknown
- #5229 — Fix false negatives for babel with preset "react-app"
Template literal interpolations:
- #4140 — Fix false positives for array literal expressions
- #4728 — Fix false positives for nested literals in unit-no-unknown
- #4953 — False positives for interpolations in CSS-in-JS
- #4987 — Fix false positives for template literal interpolations in media-feature-name-no-unknown
- #5051 — Fix autofix for switch statements within literals
- #5200 — Fix false positives for interpolation in font-family-no-duplicate-names
We recently forked the parser we use for CSS-in-JS into the stylelint organisation. We can fix all the above issues by patching and maintaining this fork.
These issues are, along with the glob issues and the one for disable comments, our most pressing ones right now. They all prevent people from using stylelint completely.
If you can help us fix our fork of the parser, please add a comment below!