When building a webapp using the technology formerly known as CSP it is common for a developer to need to edit code (e.g. classes) in the namespace associated with the webapp, as well as the webapp files (e.g. JS, CSS, and potentially also CSP / CSR). To do this a multi-root workspace can be created, e.g.
isfs://iris:user/
isfs://iris:user/csp/user?csp
There are circumstances (e.g. the Deltanji source control extension from George James Software) in which both folders should have the same folder-level settings. This is unsurprising since conceptually both are served by the same namespace.
Currently it is necessary to maintain two copies of the settings. On a default Windows install of IRIS the files would be:
On Linux and macOS the developer can probably create the latter folder to symlink to the former one, but this is harder (perhaps impossible) to achieve on Windows.
Also, in cases where a namespace hosts multiple webapps (e.g. /csp/healthshare/namespace and /csp/healthshare/namespace/fhirconfig and /csp/healthshare/namespace/services) it becomes necessary to set up and maintan multiple symlinks.
I propose we make the extension smart enough to spot when the uri isfs://iris:user/csp/user/.vscode/settings.json?csp returns FileNotFound, and in that case redirect to isfs://iris:%SYS/_vscode/USER/settings.json?csp.
Any site that needs different folder-level settings for a webapp compared to those they need for the associated namespace would manually create, say, c:\InterSystems\IRIS\csp\user\.vscode\settings.json as empty JSON (i.e. {}), and would thereafter be able to edit its contents using VS Code's Settings Editor.
When using the server-side editing paradigm namespace folders can hold folder-specific settings (see doc at https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls?KEY=GVSCO_ssworkflow#GVSCO_ssworkflow_config_folderspec).
When building a webapp using the technology formerly known as CSP it is common for a developer to need to edit code (e.g. classes) in the namespace associated with the webapp, as well as the webapp files (e.g. JS, CSS, and potentially also CSP / CSR). To do this a multi-root workspace can be created, e.g.
There are circumstances (e.g. the Deltanji source control extension from George James Software) in which both folders should have the same folder-level settings. This is unsurprising since conceptually both are served by the same namespace.
Currently it is necessary to maintain two copies of the settings. On a default Windows install of IRIS the files would be:
On Linux and macOS the developer can probably create the latter folder to symlink to the former one, but this is harder (perhaps impossible) to achieve on Windows.
Also, in cases where a namespace hosts multiple webapps (e.g.
/csp/healthshare/namespaceand/csp/healthshare/namespace/fhirconfigand/csp/healthshare/namespace/services) it becomes necessary to set up and maintan multiple symlinks.I propose we make the extension smart enough to spot when the uri
isfs://iris:user/csp/user/.vscode/settings.json?cspreturns FileNotFound, and in that case redirect toisfs://iris:%SYS/_vscode/USER/settings.json?csp.Any site that needs different folder-level settings for a webapp compared to those they need for the associated namespace would manually create, say,
c:\InterSystems\IRIS\csp\user\.vscode\settings.jsonas empty JSON (i.e.{}), and would thereafter be able to edit its contents using VS Code's Settings Editor.