Closed jimrothstein closed 4 days ago
Change title of PR to Closes #1839...
Just do devtools::document to get .Rd
files and checks should pass.
@bms63 Issue #1839
Thx for review comments.
Do a lintr::lint_package() or lintr::lint_file(your_files) and the same using styler
I don't see the .Rd
files in the PR. Are they being created? If so, you need to push those up.
Lame excuse: Switching from neovim to emacs for R.
Looks like just a couple more minor checks to fix!!
@jimrothstein almost perfect now, just need to add the words flagged by the spellcheck to inst/WORDLIST
😄
Confused. Ran spelling check several ways; with spelling::
and devtools::
. Reports no spelling errors. But RStudio still showing a few phrases 'hw', 'der_*' as spelling errors. and words NOT in WORDLIST.
Doesn't work if I manually add the words, or use spelling::update_wordlist()
@jimrothstein hmmm, looks like it passes now anyway! maybe it was just a transient issue
This Pull Request is stale because it has not been worked on in 15 days.
@jimrothstein can you please close this PR? thanks
First PR .... not quite finished, especially formatting
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
main
branch until you have checked off each task.styler::style_file()
to style R and Rmd filesinst/cheatsheet/admiral_cheatsheet.pptx
and re-upload a PDF version of it to the same xfolder.devtools::document()
so all.Rd
files in theman
folder and theNAMESPACE
file in the project root are updated appropriatelyNEWS.md
under the header# admiral (development version)
if the changes pertain to a user-facing function (i.e. it has an@export
tag) or documentation aimed at users (rather than developers). A Developer Notes section is available inNEWS.md
for tracking developer-facing issues.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()