Repository navigation
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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. |
Collaborator
|
@benkeks Thanks for the PR, please be sure to read the contributing guidelines (especially "AI-assisted contributions" section), and to use and follow the Pull Request template. |
Member
|
That looks like a great catch, thanks! |
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.
The contents shortcode filter produces unexpected character '<' errors and malformed-document warnings on ordinary input, and might remove it from the output. This is because it attempts to JSON-decode any paragraph or plain block containing a single raw inline, without checking its format.
For instance, in the smoke-test example the filter spams console output with the following ERROR/WARNING messages:
The proposed fix is to only decode raw inlines with format quarto-internal, matching the checks elsewhere in the filter.
Also, a small smoke test is added, which verifies that raw HTML survives in paragraphs and list items, that content reuse still works, and that rendering emits no errors or warnings.
Checklist
I have (if applicable):
[ ] referenced the GitHub issue this PR closes[ ] created a separate documentation PR in Quarto's website repo and linked it to this PR(does not apply)AI-assisted PR
Note: autonomous AI agents submitting PRs without human oversight are not permitted — see the Code of Conduct.