-
Notifications
You must be signed in to change notification settings - Fork 4
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
R documentation format #55
Comments
Further comments on the documentation format. The https://developer.r-project.org/Rds.html guidelines states:
This example shows an incorrect usage of #' @examples
#' \dontrun{
#' voivodeship_geom = borders_get(voivodeship = "lubuskie") # 494 KB
#' county_geom = borders_get(county = "Sopot") # 18 KB
#' commune_geom = borders_get(commune = c("Hel", "Krynica Morska")) # 11 KB
#' } These guidelines are not hard-fast for package writers, but they do follow the base-R guidelines, so I'd suggest it's worth considering them both. |
The term "Boolean" is misspelled in the documentation as "boolean" in at least one spot that I caught. |
Fixed in #59. |
If possible, we would prefer to stay with the |
To be clear, this issue is not about using it in the package but rather in the examples in the documentation itself where it's unconventional to use |
Yeah, I just mean that I would like to keep the same assignment character in all places (including examples). This is mainly due to my habit, as I also use Python. We are aware that a lot of R users prefer the For references, you can check books focused on spatial data analysis (Geocomputation with R, Spatial Data Science), examples in sf and stars packages or this interesting post. Nevertheless, thanks for this suggestion and understanding! |
Related to my review, openjournals/joss-reviews#2948,
The Guidelines for Rd files state that
\title
sections should be capitalised and not end in a period, see: https://developer.r-project.org/Rds.htmlCurrently, the ROxygen sections of the .R files are in this format:
first Second Third Word
orfirst second third word
It should instead be:
First second third word
unless there are proper names in the title for each function being documented.The text was updated successfully, but these errors were encountered: