You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to try to accommodate following use case with scala-cli: keep some scripts alongside my main project and still be able to browse/navigate them in IntelliJ.
I wasn't able to achieve it with ammonite, so I have huge hopes for scala-cli.
I tried to accomplish it by importing a script dir as bsp module into my project. Detailed steps below:
I'm not familiar with BSP that much but the generated .bsp/scala-cli.json file doesn't seem to mention external dependencies in any way.
That is expected. Generated .bsp file only stores general configuration, rest is handled under the hood. I was trying it a bit and it seems that there is a combination of issues here (some come from Intellij, some come from scala-cli) that I am trying to untangle.
I'd like to try to accommodate following use case with scala-cli: keep some scripts alongside my main project and still be able to browse/navigate them in IntelliJ.
I wasn't able to achieve it with ammonite, so I have huge hopes for scala-cli.
I tried to accomplish it by importing a script dir as bsp module into my project. Detailed steps below:
scripts
dirscala-cli scripts/script.sc
scala-cli setup-ide scripts
File
->New
->Module from existing sources
-> selectscripts
dir -> select BSP importUnfortunately, this doesn't add the
upickle
to the classpath and soujson
is not recognized.I'm not familiar with BSP that much but the generated
.bsp/scala-cli.json
file doesn't seem to mention external dependencies in any way.The text was updated successfully, but these errors were encountered: