Skip to content

Conversation

@Tofandel
Copy link
Contributor

Css variables are not property declarations but considered customProperties by the parser adding this allows for custom properties like

--my-var: #123;

To be sorted as well

Css variables are not property declarations but considered customProperties by the parser adding this allows for custom properties like
```
--my-var: srowhani#123;
```
To be sorted as well
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 94.437% when pulling 88ccec5 on Tofandel:patch-1 into d37cc47 on srowhani:master.

@coveralls
Copy link

coveralls commented Aug 26, 2020

Coverage Status

Coverage decreased (-11.1%) to 83.421% when pulling f4cc5ea on Tofandel:patch-1 into d37cc47 on srowhani:master.

@srowhani
Copy link
Owner

Seems like a nice quality of life change! Thanks for working on this. Could you add a test to accompany the feature - a simple test case being added, or an existing one modified to include css variables would do!

@Tofandel
Copy link
Contributor Author

Tofandel commented Aug 27, 2020

@srowhani Sure, but there is an issue with sass-lint, it crashes with css variables currently, sasstools/sass-lint#1310 (quite the annoying bug..)

Do you have the right to merge and publish the package on the other repo as it's marked unmaintained or should we publish a forked version?

@Tofandel
Copy link
Contributor Author

Tofandel commented Aug 27, 2020

Tests are added, they will only pass with the fix on sass-lint applied as it's currently throwing a js error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants