Is there support for multiple workingPaths?

rozsazoltan

I have a basic frontend project, and within an api subdirectory there are three different PHP mini‑projects. I would like to be able to specify a per‑project workingPath in the settings.json of a single VS Code workspace, something like this:

{
  "composer.workingPath": {
    "./../api/calculator": "./../api/calculator",
    "./../api/captcha": "./../api/captcha",
  },
}

or just:

{
  "composer.workingPath": [
    "./../api/calculator",
    "./../api/captcha",
  ],
}

Is it possible?

rozsazoltan

e.g. TailwindCSS IntelliSense supports path‑bound configurations, so in a monorepo it can offer suggestions for multiple distinct projects according to each of their own configurations - all within a single workspace.

https://github.com/tailwindlabs/tailwindcss-intellisense#tailwind-css-v4x-css-entrypoints

I want to achieve a similar setup with DevSense for VS Code, so that the different PHP projects can run independently from each other.

rozsazoltan

I know I could open them in two separate workspaces, but these are very minimal PHP projects, so it isn't worth it.

JakubMisek

You can add both folders to your VSCode workspace.

Composer commands will ask what folder you intend.