Multi-Root Workspaces, BSC Version Switching

[addison-adler]

more description to come

Might be able to borrow how this extension works?
https://marketplace.visualstudio.com/items?itemName=juliengrach.ts-multiroot

[TwitchBronBron]

That's an interesting idea. @chrisdp and I were just talking the other day about how we wanted to handle this type of situation. Where you have at least one v0 project, and at least one v1 project. Or several different incompatible versions of bsc v0 or 1.

Since we spin up a worker_thread for each project being validated, we could technically run a different version of brighterscript for each discovered project. There would be a single language server, but we could pick the latest discovered version in the workspace and use that, since it's mostly a thin shell/wrapper around the ProgramBuilder from your contributed brighterscript version.

There's some inherrant risk with incompatibilities, but I think we might be able to abstract some of that away and get better over time.

Do you mind explaining your use case?

[addison-adler]

@TwitchBronBron use-case is:

• working with multiple Roku repositories open at the same time, typically via VSC Workspaces (multi-root)
  • sometimes this is a roku repo and roku component library repos
  • sometimes this is a legacy version and then a newer version (different bsc versions)
  • sometimes this is distinct projects on different bsc versions, where I'm just using multi-root workspaces for navigation convenience
• when there are competing bsc versions, everything just implodes. Can't really work on any Roku repo because the server keeps crashing until VSC asks you to just turn it off entirely

using multi-root workspaces makes it a lot easier to copy/paste and search between repos

[addison-adler]

Spinning up a new worker_thread for each workspace root would be ideal, I think.. so that you can review worker logs separately