ScalafmtSbtReporter$ScalafmtSbtError: scalafmt: Search state exploded

[AlexITC]

This template is a guideline, not a strict requirement.

• Version: 3.4.3
• Integration: sbt
• Configuration: In the linked repo

Steps

Unfortunately, I haven't had enough time to isolate the problem but I'm linking a Scala file that crashes scalafmt, the problem seems related to snippets like:

set("&$disabled", CSSProperties()

Going to the linked repository and running sbt scalafmtCheckAll reproduces the problem.

Problem

Scalafmt formats code like this:

[info] scalafmt: Formatting 45 Scala sources (/home/dell/projects/mine/scala-webapp-template/web)...
[error] org.scalafmt.sbt.ScalafmtSbtReporter$ScalafmtSbtError: scalafmt: Search state exploded on '(∙Colors[3824:3830]', line 91 [/scala-webapp-template/web/src/main/scala/net/wiringbits/AppTheme.scala]
[error] (web / Compile / scalafmt) org.scalafmt.sbt.ScalafmtSbtReporter$ScalafmtSbtError: scalafmt: Search state exploded on '(∙Colors[3824:3830]', line 91 [/scala-webapp-template/web/src/main/scala/net/wiringbits/AppTheme.scala]

Workaround

I have had to disable scalafmt for such file.

[tusharmath]

Facing the same issue. Trying to re-create a build will post it here shortly.

[tusharmath]

Here is the repro — https://github.com/dream11/zio-http/runs/5373382741?check_suite_focus=true#step:6:50

[kitbellew]

@AlexITC @tusharmath where in the documentation did you look fo ways to deal with this? i will make sure the answer is there.

[AlexITC]

@kitbellew https://scalameta.org/scalafmt/docs/configuration.html#-format-off

[kitbellew]

perhaps that's not a good place to explain this problem. ok, I'll add it somewhere in that file, hopefully that will solve the problem

[tusharmath]

The documentation is here https://scalameta.org/scalafmt/docs/known-issues.html#deeply-nested-code

However, I don't know if my code qualifies for "deeply nested code".
I have tried all the mentioned approaches, none of them seem to work.

[tusharmath]

The other thing that I have observed is that it is happening on line number 267 in Http.scala. It doesn't matter what's on that line number, even if there is a comment, scalafmt throws this exception.