Aleks Hudochenkov

@baradusov Thank you for looking into this! It won't be enough, because later in this file also a check: https://github.com/hudochenkov/stylelint-order/blob/a274e7b160a62f72ba105c2e6e02e4a901b9be09/rules/checkAlphabeticalOrder.js#L17 Both names should be lowercased before making comparison. There is...

Thanks for providing reproducible example! `declaration-empty-line-before`, which is [set in `stylelint-config-standard`](https://github.com/stylelint/stylelint-config-standard/blob/8ea27ab960ee9eaf02ae6c689675f62c2a3ab3de/index.js#L50) removes an empty line. You need to disable this rule.

Sounds like a good idea.

Sorry for a late response. This plugin doesn't know anything about styled components. From what I see in your report, you're probably using `stylelint-processor-styled-components`. Please, refer to this issue https://github.com/styled-components/stylelint-processor-styled-components/issues/117...

@nickmccurdy stylelint supports CSS-in-JS out of the box now. Have you tried it without using `stylelint-processor-styled-components`?

@taylon please, create a separate issue with a description of your problem.

stylelint-order works great with Styled Components. I use it every day. Don't use `stylelint-processor-styled-components` and you won't see any warnings like above.

> These are not warnings, they're actual errors that fail the lint tests. Please, create an issue in `stylelint` if this happens. Help us fix these errors. I have no...

The original error is caused by using `stylelint-processor-styled-components`. It won't be fixed. I asked you to not use this processor, and you said that there are other errors. Please, report...

I think there is misunderstanding from both sides. Warning like this: > Expected -styled-mixin0 to come before text-transform (order/properties-alphabetical-order) Is definitely caused by `stylelint-processor-styled-components` because `-styled-mixin0` created from this processor....