-
Notifications
You must be signed in to change notification settings - Fork 235
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
Better errors for @includeRmd
#1089
Comments
Interesting. I think it would be even better not to touch it when the Rd roclet is running. Or not to touch it at all, until the new contents of Do you have a reprex procedure for this? |
#' Stop
#' @includeRmd "R/stop.Rmd"
#' @name stop
NULL With stop.Rmd: ```{r}
stop("foo")
``` Another case where that comes up is when I interrupt |
By the way it might be less confusing to output "Emptying NAMESPACE" the first time, rather than "Writing NAMESPACE" twice. |
I think the |
We'd want |
I think it would emit a warning, like how other tags "fail" |
IDK, this is a bit different, though, no? I think I usually want an error when the dynamic code fails. |
Maaaaybe, but I think it's better to be consistent. |
It's more clear now that this should fail with a warning since that's what child documents do. |
@includeRmd
I'm debugging errors that occur during
#' @includeRmd
. The NAMESPACE file is emptied at each error, and I need to reset it manually. Would it make sense to restore it to its original contents in case of error?The text was updated successfully, but these errors were encountered: