"al workspace compile" should be able to specify from which workspace folder to start the compilation

[ernestasjuska]

Hi,

"al workspace compile" should be able to specify from which workspace folder to start the compilation. Right now, it just compiles all app folders. This is important when there are multiple projects in the same VS Code workspace - for example we might want to skip compiling tests if there are no symbols.

Basically, I want it to be more similar to how command AL: Package full dependency tree for current project works.

Something like: al workspace compile 'Softera GPAIS for Lithuania.code-workspace' --project MainApp where --project specifies the current project folder (relative path to workspace file or absolute path).

Otherwise, we get compilation errors for app folders we did not want to compile (and this is even worse for projects with many more apps):

================================================================================
COMPILATION SUMMARY
================================================================================
Total Duration: 00:00:09
Total Projects: 2
Succeeded:      1
Failed:         1
--------------------------------------------------------------------------------

Failed Projects:
  ✗ Softera GPAIS for Lithuania.Tests (3,2s)
    Log: C:\My\Git\softera-baltic\GPAIS\GPAIS\logs\Softera GPAIS for Lithuania.Tests_20260724_101053.log

Succeeded Projects:
  ✓ Softera GPAIS for Lithuania (5,7s)
    Log: C:\My\Git\softera-baltic\GPAIS\GPAIS\logs\Softera GPAIS for Lithuania_20260724_101047.log

AL tool version: 18.0.39.10160+5e2cf204ed404fe4ae2adc02c308d60ec3fef5b0

Thanks.