feature: metadata extension works for single file #13224
Draft
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.
Continuation of
This extends
singleFileProjectContext
to ingest metadata extensions.This completely works and includes tests to prove it (with an extension but without
_quarto.yml
).However, I was concerned that it has unknown side effects:
It is a clear generalization from what we currently have:
singleFileProjectContext
takesRenderOptions
instead ofRenderFlags
.mergeExtensionMetadata
fromproject-context.ts
.config.project
. (It could havetype: default
, which should do the same thing.)mergeExtensionMetadata
into the project.