Support !exec commands in metadata-file/metadata-files - #14777
Open
jmguzmanc wants to merge 1 commit into
Open
Conversation
Allow metadata-file(s) entries to run a command instead of naming a
static file, using a new `!exec <command>` YAML tag:
metadata-files:
- !exec ./include-chapters.py --lang en
The command's stdout is parsed as YAML and merged into the project or
document metadata exactly like a regular metadata file, including
schema validation and error reporting.
Implementation:
- Register `!exec` as a custom YAML tag in both parser stacks
(core/yaml.ts and the lib-safe js-yaml-schema.ts), mirroring the
existing `!expr` tag.
- Extend the shared validation-error suppression (previously only for
`!expr`) so `!exec`-tagged values don't fail schema checks that
expect a plain path string.
- Reuse the same script-runner dispatch used by pre-render/post-render
scripts, so `.py`/`.R`/`.lua`/`.js`/`.ts` commands run through their
proper interpreter automatically; anything else falls back to a
plain process spawn.
- Any tag other than `!exec` (e.g. a stray `!expr`) now fails with a
clear "unsupported tag" error instead of an internal TypeError.
Includes unit tests for the tag parsing and a smoke test covering a
project with both a plain-file and an `!exec` metadata-files entry.
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Allow metadata-file(s) entries to run a command instead of naming a static file, using a new
!exec <command>YAML tag:or
The command's stdout is parsed as YAML and merged into the project or document metadata exactly like a regular metadata file, including schema validation and error reporting.
Checklist
I have (if applicable):
!execcommands inmetadata-file/metadata-filesquarto-web#2145AI-assisted PR