SearchStateExploded error

[cb372]

Version: 0.4.10
Integration: coursier, via my poor man's sbt plugin
Configuration: maxColumn = 120; project.git = true

[warn] Error in /Users/chris.birchall/code/mailgun-api-client/src/test/scala/com/ovoenergy/mailgun/model/events/EventsResponseSpec.scala: org.scalafmt.Error$SearchStateExploded: Search state exploded around line 59

The input is this ridiculously verbose test I just wrote.

[olafurpg]

This is a known issue, see #140 for an explanation. #582 is related. For config style arguments (like in your test) I don't think this should be too hard to fix. Turns out this is a blocker for #588, so I might take a look at it soon.

ps. 120 max column is a lot, you must have a wide display :p

[cb372]

120 max column is a lot

I thought you would pick up on this. I know, I'm a monster!

Thanks for the quick response.

[olafurpg]

Good news @cb372, see https://github.com/olafurpg/scalafmt/pull/621

Your ridiculously verbose test has now become a scalafmt unit test :D The change is limited to Term.Apply with a large number of arguments and large bodies. In those cases, scalafmt will force "config style" and dequeue the search space at the start of every argument. The optimization is controlled by two magic numbers, which are configurable inside runner.optimizer. I have no idea if the defaults are any good.

I'll include this for v0.5!

[olafurpg]

Closing this since your particular example now formats easily.

[cb372]

Yay! Thanks for the fix! I love your flamegraph-style test output by the way.