More helpful error messages when Quarto chunk options are mis-specified #2433
Replies: 1 comment 2 replies
-
This is indeed annoying. I wrote a custom handler exactly for this case a few months ago but for whatever reason it's not getting called. I'll create an issue to track. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I posted this on the RStudio community as well, but figured out it should actually be here.
If you mess up when specifying your Quarto chunk options and use
=
instead of:
in one of your code chunks (cough, former RMarkdown users), you will get a pretty impenetrable (to me) error about YAML. For example:Gives the error
I spent way too much time looking for errors in my header YAML, forgetting that those
#|
comments are basically YAML now, too. One of the problems is theline 3
part. I was looking in the third line of my Quarto document!Not sure if it would be possible, but it would be awesome to have an error message that said something like
Scanner error: while scanning the options in chunk 1, ...
Beta Was this translation helpful? Give feedback.
All reactions