-
Notifications
You must be signed in to change notification settings - Fork 3
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
Closes #111 dataset contents ref pages #130
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- A comment should be added to the
R/*.R
that these are generated and shouldn't be edited manually. README.md
should be updated to describe the new documentation process.
@vbshuliar once you update |
@manciniedoardo @bundfussr Please take a look at the updated version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @vbshuliar - I tested the actual process and looks great. I've added a couple of comments.
In addition to the above I also tried rendering the site. Looks good, but can you please restructure the reference page so that it mentions datasets and not functions:
Edit: get_terms()
should still be under functions.
I updated the layout as you requested. Please, proceed with the rereview @manciniedoardo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use a JSON file?
Then it is possible to see changes in github.
@@ -0,0 +1,134 @@ | |||
# Load the XLSX file with metadata |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a header describing the purpose of the script?
|
||
# Create documentation for the current dataset | ||
doc_string <- paste( | ||
sprintf("# This file is automatically generated."), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add more information? For example:
sprintf("# This file is automatically generated."), | |
sprintf("# This file is automatically generated by data-raw/create_sdtms_data.R."), | |
sprintf("# For updating it please edit inst/extdata/sdtms-specs.json and rerun create_sdtms_data.R."), |
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the
devel
branch until you have checked off each task.styler::style_file()
to style R and Rmd filesdevtools::document()
so all.Rd
files in theman
folder and theNAMESPACE
file in the project root are updated appropriatelyNEWS.md
if the changes pertain to a user-facing function (i.e. it has an@export
tag) or documentation aimed at users (rather than developers)pkgdown::build_site()
and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.lintr::lint_package()
R CMD check
locally and address all errors and warnings -devtools::check()