You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
When rendering a document with R code in YAML with quotes like this, rendering YAML fails with the warning pandoc warning [WARNING] Could not parse YAML metadata :
This is because, prior to knitting, redoc wraps R code in tags that include a quoted class. If you render the document with clean=FALSE, the pre-processed file will look like this:
Currently working on a solution. I previously used pandoc-style native spans, which look like this, but switched to HTML style because something was conflicting with those:
[`r Sys.Date()`]{.redoc #redoc-inlineccode-1}
The yaml package always defaults to writing single quotes, so maybe I should always re-write header YAML as single quotes to avoid this? In any case, using single quotes will temporarily solve the issue.
The text was updated successfully, but these errors were encountered:
Thanks @noamross ! I'll try that out and make sure it works. That's annoying that the type of quote can make a difference, and I'll need to remember to try different types of quotes when I see odd behavior.
@rmflight this relates to your problem in #41
When rendering a document with R code in YAML with quotes like this, rendering YAML fails with the warning pandoc warning
[WARNING] Could not parse YAML metadata
:This works if the YAML if placed in single quotes:
This is because, prior to knitting,
redoc
wraps R code in tags that include a quoted class. If you render the document withclean=FALSE
, the pre-processed file will look like this:Currently working on a solution. I previously used pandoc-style native spans, which look like this, but switched to HTML style because something was conflicting with those:
The
yaml
package always defaults to writing single quotes, so maybe I should always re-write header YAML as single quotes to avoid this? In any case, using single quotes will temporarily solve the issue.The text was updated successfully, but these errors were encountered: