I like you use links for more information about code in documentation 👍
But if I compile the documentation via devtools::document() I get:

> devtools::document()
Updating trias documentation
Loading trias
Writing NAMESPACE
Writing NAMESPACE
Writing countYearNativerange.Rd
Warning message:
Can't find help topic 'countYearProvince' in current package

This means the link is broken. R thinks your link is in trias package. Is grofwild a package? Then you can use something like this \code{\link[MASS]{abbey}}? But I don't think it is a package. Then maybe a classic Markdown-style link solves the problem, e.g.:

#' See more about the markdown markup at the
#' [Commonmark web site](http://commonmark.org/help)

This vignette is very helpful: https://cran.r-project.org/web/packages/roxygen2/vignettes/rd-formatting.html#links

I like you use links for more information about code in documentation 👍

I just copied that part from @eadriaensen => should I include her as contributor as well ?

Is grofwild a package?

reportingGrofwild is a package, yes! However it is not published to cran or any other package repository.

@damianooldoni the link to the reporting-grofwild function has been rewriten but I don't know how to check if its working.
The installation of the modified trias package runs without new errors (expect the error described here #65 (comment)).

You don't need and don't have to source within a package. Installing a package and loading it makes all functions available for tests as well.

Run devtools::install() and ´library(trias)(the latter command needed the first time) after you changed something in the functions and you have all functions ready to be used. So, in package development,devtools::install()is your best friend,source` your enemy 😄

When I use devtools::install() with the script without plotly::layout() i get this error:
Note: possible error in 'layout(xaxis = list(title = x_lab, ': unused arguments (xaxis = list(title = x_lab, tickangle = "auto"), yaxis = list(title = y_lab, tickformat = ",d"), margin = list(b = 80, t = 100), barmode = ifelse(nlevels(summaryData$first_observed) == 1, "group", "stack")) at indicator_native_range_year.R:104

I suspected this was due to R thinking layout from the package graphics should be used, while the importFrom line clearly states layout should come from the plotly package (@importForm plotly ggplotly, layout).
Adding plotly:: before layout solves this problem. Any idea why this is ?

somehow rebuilding the NAMESPACE (found out some functions I imported were missing) does not include plotly to the list. Maybe this is the cause??

This is not a test. Testing plotly output is practically impossible or quite challenging, but you can test the data slot, and the fact that you get always a list and not something else... Writing tests is something which takes time, I know, but it helps making your code more robust and user friendly. For example, testing the input types, See other tests functions in trias package to understand what I mean. But I don't blame you if you don't want to spend time on the tests, I will do it.

This is not a test.

all jokes aside, I simply used this to test if the function worked.