-
Notifications
You must be signed in to change notification settings - Fork 323
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
build_reference() changes broke something? #1930
Comments
Looking at https://github.com/taxonomicallyinformedannotation/tima-r, I have two questions (not necessarily implying these are the causes of the error!):
#' @param annotationTableWeightedBio should be #' @param annotationTableWeightedBio description of the parameter blabla |
Hi, Thank you for your reply and for having a look directly at the repo! :) I actually removed them for the website to build (see taxonomicallyinformedannotation/tima-r@fa29fa2) When regenerating them locally with devtools, the issue persists. Yup, nothing is documented for now... |
So, it seems pkgdown assumes the docs have to be complete 😉 If I create a package ( #' Title
#'
#' @param a
#'
#' @return
#' @export
#'
#' @examples
test <- function(a) {
a
} and then If I make the script #' Title
#'
#' @param a description
#'
#' @return something
#' @export
#'
#' @examples
test <- function(a) {
a
} then document then build the website, things are fine. So at the current state yes you first need to fill the roxygen2 tags (or add |
Oh wow, this is new then 😅 Guess I'll try documenting and coming back in case! Thank you very much for your help! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I can confirm filling the skeletons with |
This comment has been minimized.
This comment has been minimized.
We will obviously fix this; @maelle has provided you with a work around in the interim. |
It's the empty |
Hi,
I read the changelogs and it looks like the build_reference() function now errors, without providing an understandable message error.
I re-installed version 1.6.1 and it worked well
But when using version 2.0.0:
which then leads to:
Any hints?
The text was updated successfully, but these errors were encountered: