Artūras Šlajus
Artūras Šlajus
CI run failed (https://github.com/scalameta/metals/actions/runs/15799102190/job/44613791634?pr=7544#step:5:26417), but I can't find the actual error and locally the tests run just fine for me: ``` tests.mill.MillLspSuite: + basic 36.725s + new-dependency 41.994s + error...
> It might be flaky, the Mill tests somehow are. Let's see if they pass now It seems an unrelated test now failed due to flakyness. Can we get this...
I've tested it out, MCP server is added automatically and works. 
Had an idea: what if we would disambiguate the metals MCP server by giving them names that are full paths to the project? Then when updating the file we could...
@kasiaMarek can you elaborate on whether `out/test/compiledClassesAndSemanticDbFiles.dest` should contain classes from both `main` and `test` modules or there should be separate `out/main/compiledClassesAndSemanticDbFiles.dest` and `out/test/compiledClassesAndSemanticDbFiles.dest` with their respective files?
Restructured as requested.
I've made the requested changes and introduced `Route.staticTotal`. While it is possible to misuse it, you have to explicitly opt-in into it and I find it useful.
Turns out there is a way to require a type to be singleton! https://www.scala-lang.org/api/2.13.6/scala/ValueOf.html Thus no extra tests are needed, right?
Added compilation tests.
Just to clarify - is there anything left to do before merging this?