Workaround for rendering reports in Quarto #520
Merged
Conversation
This file contains 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.
All
{gt}reports (agent, informant, multiagent) are now post-processed withgt::fmt(fns = identity)to prevent treating them as data tables in Quarto. More formally put, reports rendered in Quarto no longer come with any<div data-qmd="...">. I've also added a manual testtests/manual_tests/test-quarto-render.Rthat checks for this.This PR also fixes an issue with
<code>in reports inheriting purple color from the Quarto theme.Reprex from #518
Fixes: #518