Feature request: better support for multi-root workspaces (relative paths) about vscode-deploy-reloaded HOT 2 OPEN

A workaround to this issue is to create a .vscode folder at the root of each sub-projects and put vscode-deploy settings in a settings.json file there.

But in my opinion this should be a temporary solution only: .vscode folders are not used (even not created) by vscode in the case of multi-root workspaces, so having to create such a folder sounds strange.

from vscode-deploy-reloaded.

Just a note on multi-root

There are two types of settings: "Resource" and "Editor"

Resource settings apply to files and folders, and are still the main place to put settings for things like FTP, which deals directly with resources.

Editor settings are things like "window.zoomLevel" which effect everything. Something like an "enable" flag would be appropriate here if an option is available to disable the whole extension for a project.

Using a resource setting for sftp makes sense, as the folder then becomes the (relative) localPath to map to the remotePath.

Alternatively, using the editor-wide settings, you'd have to define the local path manually and probably have to use absolute file-system paths, which not many people would enjoy.

Using both types of settings is correct in multi-root, depending on it's purpose; it is just challenging to think about which settings go where.

from vscode-deploy-reloaded.