Add postcss-sorting integration

[nkt]

No description provided.

[matype]

@nkt Thank you for you PR! Good stuff :)

But, I have a question. Are you taking into account using with @include and @extend in SCSS code, or @apply rules?

There is a possibility to change source code destructive by sorting declarations. Please see also #3 (comment) .

Thanks.

[nkt]

@morishitter maybe I should add check for sass right here?

if (params.isSass || !Array.isArray(sortOrder)) {
  return;
}

[matype]

I'd like to consider with at-rules e.g. @apply, @include of SCSS and @mixin of postcs-mixins. I think, at-rules in declaration nodes of PostCSS should be on the top of its declaration.

.selector {
  font-size: 12px;
  max-width: 280px;
  @include truncate();
}

The above code will be formatted to the following code.

.selector {
  @include truncate();
  max-width: 280px;
  font-size: 12px;
}

What do you think?

[nkt]

This is already supported by postcss-sorting. I've updated tests.

[nkt]

Here is docs: https://github.com/hudochenkov/postcss-sorting#at-rules

[nkt]

postcss-sorting also supports grouping, but this feature not supported by stylelint 😞

[matype]

Wow, nice! I wish stylelint will support it.

[jeddy3]

FYI, stylelint does support property groups.

[matype]

@nkt Thank you so much ;)

[jeddy3]

This is fantastic! Great job :)

You might be interested in keeping an eye on this proposal for a companion plugin to declaration-block-properties-order called stylelint-block-non-properties-order. The hope is that it'll work alongside declaration-block-properties-order to lint the order of non-property things like nested at-rules, nested rules and variables. It's early days yet, but hopefully something will come of it :)

[jasonlong]

Thanks @nkt!