space-after-declaration vs comments

@mishanga @kizu, I can really use your advice here.

Take this code as an example:

a {
  color: tomato;      /* comment */
  position: fixed;
  /* comment */
  top: 0;
  left: 0;

  &:hover {
    color: black;     // comment
    top: 100%;
  }
}

What should be the result after processing this code with settings:

1. 'space-after-declaration': ' ' and
2. 'space-after-declaration': '\n'?

Related issue: #232

[kizu]

I’d say that when the comment is on a line with another declaration, then, from a user’s standpoint, it is a part of a declaration as it is related to it.

The comments themselves, I’d say, should have their own space-before and space-after, so when there is a block-level comment, it should be still on its own line.

The preprocessor-style inline comment is tricky, I’d say that it should prevent the lines to join in all cases. Maybe we could add a preprocessor-specific option for converting such inline comments when there is something that should go after them.

So, as a user, I would expect:

1. 'space-after-declaration': ' ':

   a {
     color: tomato;      /* comment */ position: fixed;
     /* comment */
     top: 0; left: 0;
   
     &:hover {
       color: black;     // comment
       top: 100%;
     }
   }
   

2. 'space-after-declaration': '\n': just the initial result, as I would expect the inline comments to be treated as the part of declaration.

Also, I would expect the following options: space-[before|after]-[block|inline]-comment, where the inline comment is the comment placed on the same line as a declaration (or any other entity), while block comment is a comment that do not have any non-whitespace symbols on the line it starts from.

[tonyganch]

@kizu @mishanga, thank you