-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore the case characters order #78
Comments
I think this plugin should ignore property case when sorting. I haven't thought about this before, because lower cased properties are kind of default in our industry :) Your case is totally valid, a plugin should ignore the case of properties. |
@hudochenkov If change this condition
to firstPropData.unprefixedName.toLowerCase() === secondPropData.unprefixedName.toLowerCase() is it will be enough to resolve issue? I tested it and it seems ignoring case without breaking anything. But if using default |
@baradusov Thank you for looking into this! It won't be enough, because later in this file also a check:
Both names should be lowercased before making comparison. There is also a check for
|
Hi, I've got a specific problem.
I'm trying to implement stylelint into my environment (which is for development newsletters and based on Foundation for Emails). There is specific hacks for developing newsletters for legacy email clients. And one of them is margins support in Outlook. It requires to use a "margin" property with first capital letter.
For example -
Margin: 0 auto;
, so the total style block looks like this:It's necessary to capital "Margin" follows after lower one. But in this case I'm getting alphabetical error. I suppose there is a some regexp that looks like [A-Za-z]. Is there any chance to change this behavior?
Thanks
The text was updated successfully, but these errors were encountered: