-
I have basically run configurations defined in build.sbt file, they run scala code with different arguments per each run config. Example: val prems = inputKey[Unit]("premium small trace")
prems := (Compile / run).fullInput(getArguments("LF481773_1Min-Part0.ttl", premiumPath)).evaluated to run it i execute this command What should i do to be able to debug a task defined in build.sbt? I have seen this configuration option in nvim config, but i do not want my run configuration to be defined or saved outside of project folder. {
type = "scala",
request = "launch",
name = "run-someip",
metals = {
mainClass = "Main",
runType = "run",
buildTarget = "root",
--args = { "firstArg", "secondArg", "thirdArg" }, -- here just as an example
},
}, Can you advise me on this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey @gogamid, I'm not actually sure if these are processed or not, but one thing to actually try would be to use sbt as your build server instead of Bloop. You can use @adpi2 do you by chance know if this would work with sbt BSP? |
Beta Was this translation helpful? Give feedback.
Unfortunately it would not work. There is no way currently to configure the debugger outside of the nvim config (or VSCode launch configuration). This is not great and I wonder how we could improve this. Would it make sense to use using directives to embed the debug configuration into Scala files? (maybe I should open a discussion in Metals about this)