Force annotations onto their own lines for block expressions and parameter clauses

[kiritsuku]

From @daniel-trinh on March 2, 2014 19:48

Annotations for expressions in blocks and parameter clauses currently are placed on the same line:

def asdf(
  @annotation one: Int,
  @a @b(c) two: String
)

class A extends B {
  @SomeImportantAnnotation(param = true) override val param: Int = 1

  @NotSoImportantAnnotation(param = false) val description: String = "Not so important"
}

Instead, it should be formatted as..

def asdf(
  @annotation 
  one: Int,
  @a 
  @b(c) 
  two: String
)

class A extends B {
  @SomeImportantAnnotation(param = true) 
  override val param: Int = 1

  @NotSoImportantAnnotation(param = false) 
  val description: String = "Not so important"
}

This would most likely only affect parameters that are already placed on their own line, so
something like this wouldn't be affected:

def asdf(@annotation one: Int, @a @b(c) two: String)

stays as..

def asdf(@annotation one: Int, @a @b(c) two: String)

Implementation details note: this needs to be implemented without breaking the AlignParameters feature

See here for similar issue on original branch: #91

Copied from original issue: daniel-trinh#12

[kiritsuku]

From @bambuchaAdm on March 2, 2014 22:57

Don't you think here

def asdf(
  @annotation 
  one: Int,
  @a @b(c) 
  two: String
)

better construction will be set second annotation @b(c) to next line ?

[kiritsuku]

From @daniel-trinh on March 2, 2014 23:0

Yea, good catch, I'll fix the description

[kiritsuku]

From @bambuchaAdm on March 4, 2014 0:25

Test for annotation are green. Maybe tommorrow, I will clean up tests. I think it will be quick.

[kiritsuku]

From @bambuchaAdm on March 4, 2014 8:26

On making tests green, i ran into test for #28.

Maybe we should introduce configuration parameter ?

[kiritsuku]

From @daniel-trinh on March 4, 2014 18:13

Hmm, I think we should either keep it as is (force annotations onto their own line), or modify it so that it preserves newlines implicitly.

I'm not a fan of more configuration parameters, because there are much more interesting problems to solve than thinking about how to format Scala code -- having one reasonable default is good enough IMO.

[kiritsuku]

From @daniel-trinh on March 11, 2014 1:10

@bambuchaAdm How's this feature looking? Scala 2.11 release is nearing, #4 and #12 are pretty useful features to try and include into a 0.15.0 non-snapshot release.

[kiritsuku]

From @ConnorDoyle on June 23, 2014 23:1

I would love to see this change in scalariform. Without this fix, we have some lines that exceed 160 columns!

[kiritsuku]

From @patrikvarga on March 16, 2015 13:15

+1, this is very annoying, especially that it is not conforming the Scala Style Guide and thus makes the following statement in the documentation invalid:
"Scalariform is compatible with the Scala Style Guide in the sense that, given the right preference settings, source code that is initially compiliant with the Style Guide will not become uncompliant after formatting."

[mjaghouri]

I would like to preserve annotations as they are defined, i.e., whether they have their own line or are maybe put on the same line. Currently, a specific definition with multiple (somewhat long) annotations is reformatted into one very long line, which is undesirable.
Maybe also fine to just force every annotation on its own line.