-
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
function and variable names are in backquotes #191
function and variable names are in backquotes #191
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.
Hi @sonalijain17, thanks for working on this.
- The spellcheck is failing because when you (correctly) changed
ADIOP
to ADIOP in the standards vignette, the fact that the backquotes are gone - i.e. the this is now "text" and not "code" - means that our spelling checker is now analysing the word to see if it's a dictionary word, or if it's not. Given that "ADIOP" is not in the dictionary, the spellcheck flags it as a spelling error. But we know it's not a spelling error, so we want to add it to our own personal dictionary, which we can do by editing the fileinst/wordlist
. please could you go ahead and do that? - The other check that is failing can be ignored.
- In
derive_var_studyeye()
reference page please could you ensure "SCTESTCD" is in backquotes too? - In derive_var_afeye please could you ensure "AFEYE" is always in backquotes?
- When on the "Reference" page on the website, I clicked on any of the example datasets, and I can still see datasets in backquotes under "Source" - see here for instance. Please could you edit that too? You can see this page is generated by the script
R/data.R
.
Hi @manciniedoardo, thanks for reviewing and providing the comments. |
I agree thanks. Please re-commit and we can see if the checks now pass 😄 |
Hi @sonalijain17 the man/Roxygen check is failing - please could you click on details and that should explain how to fix it thanks. |
Updated based on the explanation. The check is passed now. |
Closes #173
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()