AlexHaxe

keeping the line break before multi line strings is doable, but currently that would lead to indentation of its first line, which is probably not much better.

I guess it just never came up when reworking `()` and `{}` options. Also since nobody complained about it, there was no reason to touch it - until now... :)

typedef != anonType Currently there is no setting for typedef wrapping, so `anonType` only applies to unnamed / anonymous structure definitions.

I am not sure I want one set of rules for both. Anonymous types can occur as type hints for variables, fields and function parameters. And most of them are...

There are two wrapping rules that could apply to that line: call parameter and OpAdd chain, for now the first one wins. Wrapping code currently doesn't have a weighting function...

Well, `+` already implies two items. And despite it being a valid OpAdd chain or not, wrapping at `+` and wrapping at `,` both produce a valid output below max...

that's not a bug, that's a feature :smiley: see #292 though, one might argue whether `emptylines.afterFileHeaderComment` should default to 1 or 0

yep, when there is 10 or more items it will switch to `fillLine` instead of `onePerLine`.... At some point `fillLine` has to happen, because if you have dozens of items,...

Currently formatter only deals with removal or addition of whitespace. It doesn't rearrange, add or delete tokens from your sources. Introducing a new token into or making edits to a...

Hi, I transferred your issue over to formatter's issues. right now there is no option to stop line breaks after last element in "onePerLine" mode And there is also no...