[Sync to prerelease] Treat any non-markdown engine as computational in freeze guidance - #2129
Merged
Conversation
) The _freeze guidance named knitr/jupyter/julia as the executing engines, but since Quarto 1.9 Engine Extensions a page can use a custom engine beyond those. markdown is the only non-executing engine (the no-op default), so a custom-engine page would be misread as non-computational and risk deleting a real freeze. Reframe as an invariant: markdown means no execution, any other engine executes. (cherry picked from commit 21ec13a)
Member
|
/deploy-preview |
Contributor
Author
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-2129.quarto.org |
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
1 participant
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
Sync of #2128 to
prerelease.Original PR
Treat any non-markdown engine as computational in freeze guidance
The
_freeze/guidance in.claude/rules/quarto-web-workflow.mdnamedknitr/jupyter/juliaas the executing engines. But since Quarto 1.9's Engine Extensions a document can use a custom engine beyond those, andmarkdownis the only non-executing engine (the no-op default when nothing else claims the file).With the old allow-list phrasing, a custom-engine page would be misread as non-computational — and its real freeze could be deleted as "vestigial".
Reframe as an invariant:
quarto inspect'senginesarray ismarkdown⇒ no execution; any other engine ⇒ the page executes code (with knitr/jupyter/julia as examples, not an exhaustive list).Follows #2124.