Is reformatting: ```import kotlinx.coroutines.CoroutineScope internal abstract class MyParentClass...

# ktlint

[zak.taccardi]

Is reformatting:

import kotlinx.coroutines.CoroutineScope

internal abstract class MyParentClass(
    string: String
)

internal class MyChildClass(
    scope: CoroutineScope
) : MyParentClass(
    "hello"
), CoroutineScope by scope

to be:

import kotlinx.coroutines.CoroutineScope

internal abstract class MyParentClass(
    string: String
)

internal class MyChildClass(
    scope: CoroutineScope
) : MyParentClass(
    "hello"
),
    CoroutineScope by scope

a bug? the error is Missing newline after "," and violates the wrapping rule

[zak.taccardi]

I submitted Additional parent classes are forced to be on a new line always. Is this intentional?

[Paul Dingemans]

Tnx for filing the bug. Will have a look in coming days.

[Paul Dingemans]

What is your opinion about formatting generic types having multiple annotations? Please provide your input in https://github.com/pinterest/ktlint/issues/1725.

The remark of the issuer was that code below:

data class FooRequestDto(
    val data: List<@Valid @NotNull FooDto>,
)

is formatted by ktlint as:

data class FooRequestDto(
    val data: List<@Valid @NotNull
    FooDto,>,
)

Of course it should be clear that I totally agree with that. In the issue, I have proposed to format this like:

data class FooRequestDto(
    val data: List<
        @Valid
        @NotNull
        FooDto,
    >,
)

Please, add your remarks or counter proposals in the issue. Thanks!