extend setting 'headerTemplate' with scope... #184
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.. 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