Open ckipp01 opened 1 year ago
Using scala-debug-adapter
is probably the way to go. But we need a Scala 2.13 version of it, which is currently not released.
Today, scala-debug-adapter_2.13-3.0.6
was release.
After some conversations on the Scala Tooling Summit, I learned that Metals plans to add support to start the Debug Adapter directly, as all information about the buildTarget is already present. Hence, we don't need to implement the debugProvider
capability.
I haven't found any evidence, that Metals is indeed providing debug adapter support directly, so I think this issue might be still valid and any help would be appreciated.
I assigned myself to this issue since I started working on it.
For what it's worth, Mill doesn't seem to need to implement debugProvider
, since this ticket at Metals has been moved to In Progress:
This is a feature request related to using Mill as a BSP server. Currently Metals is a
runProvider
andtestProvider
, but not adebugProvider
as you can see in the initialize response here:This means that tools like Metals can't offer debugging in the editor for you Mill project.
Potential solutions
Probably an integration with https://github.com/scalacenter/scala-debug-adapter.