With a simple workspace (only one root), the settings of project_root/.vscode/settings.json will be used for all Markdown files. (if markdown-pdf.headerTemplate isn't set, Userlevel settings or Default settings will be used).
At this point, same behaviour as now.
But when you add project_root/sub2 as separate folder to the workspace:
the settings of project_root/sub2/.vscode/settings.json will be used for project_root/sub2/sub2.md.
For project_root/root.md the settings from project_root/.vscode/settings.json will be used.
For project_root/sub1/sub1.md the Userlevel/default settings will be used, as long as you haven't set separate workspace level settings (inside the .code-workspace file for the loaded workspace)
in that pull request, I only changed headerTemplate because currently this is the only option that I need. but you could also change the/some other options, to made them individual set able on workspace-root level!
.. scope: "resource" will able to setup separate .vscode/settings.json per workspace folder
with this small change single options can be set on workspace-folder level. An example: The following FOLDER structure
With a simple workspace (only one root), the settings of
project_root/.vscode/settings.json
will be used for all Markdown files. (ifmarkdown-pdf.headerTemplate
isn't set, Userlevel settings or Default settings will be used). At this point, same behaviour as now.But when you add
project_root/sub2
as separate folder to the workspace:project_root/sub2/.vscode/settings.json
will be used forproject_root/sub2/sub2.md
.project_root/root.md
the settings fromproject_root/.vscode/settings.json
will be used.project_root/sub1/sub1.md
the Userlevel/default settings will be used, as long as you haven't set separate workspace level settings (inside the.code-workspace
file for the loaded workspace)This could maybe also a solution for #173
Extended Example
project_root/.vscode/settings.json
project_root/.vscode/ws.code-workspace
project_root/sub2/.vscode/settings.json