Repository navigation
feat: add get_project_metadata for QUARTO_EXECUTE_INFO - #19
Merged
Merged
Conversation
mcanouil
marked this pull request as ready for review
October 29, 2026 14:48
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
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.
Several extensions read the
QUARTO_EXECUTE_INFOfile themselves to get the project'swebsiteandbookmetadata, each with its own error handling.This adds
get_project_metadatatometadata.lua, so they can share one tested reader.It returns the
format.metadatatable.When the variable is set but the file can't be used, it returns
niland one of'file is unreadable','file is empty','invalid JSON'or'no format.metadata table'.When the variable is unset or empty, it returns
nilalone, so single documents stay silent.The module doesn't log or cache, and each extension decides whether to warn.
A decoder that returns
nilcounts as invalid JSON, so quarto-cli and q2 report the same reason.get_project_repo_urlnow builds on it and takes an optionalformat_metatable, so an extension that already read the file doesn't read it again.A side effect: JSON that isn't an object now gives
nilinstead of an error that stopped the filter.The tests stub
os.getenvandquarto.jsonand cover each failure path, website only, book only and both.