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
Is your feature request related to a problem? Please describe.
Recently in Metals a pr was merged that offers support for multi-root workspaces. I have a couple different repos that have a main project contained in one directory and a set of scripts contained in another. It used to be that before I always had to re-open that subproject individually to get support. Now with this support, it's no longer necessary to do that! One limitation currently though when using scala-cli is that it's really difficult to actually know if you're looking at the correct build targets or not for your project since they are just random. For example I have a project with a skan and scripts directories. Each their own separate build. Here are the build targets for them:
project_a67e43e310-cf755cd196 for skan
project_a67e43e310 for scripts
So when I jump back and forth between them it's really hard to know if Metals correctly identifies them.
Describe the solution you'd like
I'd be nice if the build target name was derived maybe from the script or the directory that contains it? For example in my case it'd be much clearer if it was:
skan_a67e43e310-cf755cd196 for skan
scripts_a67e43e310 for scripts
This might help avoid some confusion for users that are using scala-cli projects with multi-root projects.
Describe alternatives you've considered
Just double-checking the numbers are different and hoping it all works.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Recently in Metals a pr was merged that offers support for multi-root workspaces. I have a couple different repos that have a main project contained in one directory and a set of scripts contained in another. It used to be that before I always had to re-open that subproject individually to get support. Now with this support, it's no longer necessary to do that! One limitation currently though when using scala-cli is that it's really difficult to actually know if you're looking at the correct build targets or not for your project since they are just random. For example I have a project with a
skan
andscripts
directories. Each their own separate build. Here are the build targets for them:project_a67e43e310-cf755cd196
forskan
project_a67e43e310
forscripts
So when I jump back and forth between them it's really hard to know if Metals correctly identifies them.
Describe the solution you'd like
I'd be nice if the build target name was derived maybe from the script or the directory that contains it? For example in my case it'd be much clearer if it was:
skan_a67e43e310-cf755cd196
forskan
scripts_a67e43e310
forscripts
This might help avoid some confusion for users that are using
scala-cli
projects with multi-root projects.Describe alternatives you've considered
Just double-checking the numbers are different and hoping it all works.
The text was updated successfully, but these errors were encountered: