-
Notifications
You must be signed in to change notification settings - Fork 459
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
New option: rule-delimiter #210
Comments
Alas, there is no way to achieve this with current settings. |
Big +1 from me. I just spent quite a while manually adding new lines in! |
Is this implemented with the new V3? I can't find the option in the docs. |
@lefoy, nope |
Any idea when this will be implemented? Is it planned for the stable V3 release? |
+1 from my side |
+1 would love this |
+1 |
+1 from me too |
Hello, do we have an ETA for this? would be awesome |
There is no ETA for this option. |
Huge +1. |
+1 |
+1, would love to have this |
@thebugs I think it should accepts number of lines as parameter, not boolean. |
+1 for number of lines instead of boolean |
I've updated gist. Now it accepts number of lines as parameter |
@thebugs Thank you! Good job! |
@thebugs Thanks! Looks like there is a small issue though if you run csscomb more than once it keeps adding an extra line below the rule, so if you run it 3 times there are three blank lines under each rule. |
@FernE97 I use only scss. So if there are issues with other syntax - sorry. |
@thebugs I am using scss as well and that is where I'm noticing the issue. Wonder if there is something in my Here is my config file minus the huge sort-order array. {
"remove-empty-rulesets": true,
"always-semicolon": true,
"color-case": "lower",
"block-indent": " ",
"color-shorthand": true,
"element-case": "lower",
"eof-newline": true,
"leading-zero": true,
"quotes": "single",
"sort-order-fallback": "abc",
"space-before-colon": "",
"space-after-colon": " ",
"space-before-combinator": " ",
"space-after-combinator": " ",
"space-between-declarations": "\n",
"space-before-opening-brace": " ",
"space-after-opening-brace": "\n",
"space-after-selector-delimiter": "\n",
"space-before-selector-delimiter": "",
"space-before-closing-brace": "\n",
"strip-spaces": true,
"tab-size": true,
"unitless-zero": true,
"vendor-prefix-align": true,
"rules-delimiter": 1
} |
+1 would really love to see this |
What is the current status on this? How can I help make this a thing? |
+1 |
@SpencerCarstens, the most recent pr is #405 |
+1 |
1 similar comment
+1 |
+1 |
1 similar comment
+1 |
+1 |
10 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
I'm temporarily locking the conversation to avoid more +1's. |
Moved from #209:
I guess we should add an option like
rule-delimiter
which will set spaces between rulesets and media queries (this has been already discussed in #92).It seems to me that this option should be more important than
space-after-declaration
(see #197).So we can have, for example:
{ 'space-after-declaration': 1, 'rule-delimiter': '\n\n' }
The text was updated successfully, but these errors were encountered: