-
-
Notifications
You must be signed in to change notification settings - Fork 975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An output format argument with no default causes rmarkdown:::default_output_format to fail with cryptic error message. #2407
Comments
Thank for sharing your experience.
Is this happening only on RStudio IDE while knitting ? Or also in VS CODE. I understand it does not happen in Console when doing the function We should probably try to fix in this function
yeah sorry. I don't think this is documented. We don't have a lot (yet) on custom format . Glad you managed to create one!
That is so cool !! 🎉 |
Yes, this is a RStudio-only thing. VSCode-R extension doesn't call |
That did fix it for me; the new dashboard is now deployed here. |
I ran into this developing a custom output format that worked fine from the console, but threw an error only when using the ‘knit’ button in RStudio.
Upon clicking the button I see this in the console:
I found the cause here in
default_output_format()
As you can see here the
repo
arg of mygithub_issue
format had no default value.So we get:
Created on 2022-09-02 with reprex v2.0.2
I think if I add a default to my output format all should be well. This was just a little hard to figure out and I didn’t find it documented anywhere, my apologies if this is so.
Maybe this case could be detected an some kind of more useful error thrown?
PS I drafted this and submitted this issue in RStudio with my
github_issue
format. An amazing job has been done with how extensible rmarkdown output formats are! 😄The text was updated successfully, but these errors were encountered: