-
Notifications
You must be signed in to change notification settings - Fork 8
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
plotStudy and getPlottingData functions accept parameter testID. #4
Conversation
curadomr
commented
Aug 9, 2021
- Param testID is set to NULL in plotStudy as default.
- Output of getPlottingData provides test result (if testID is NULL, no result object is provided in the plottingData list)
- Param testID is set to NULL in plotStudy as default. - Output of getPlottingData provides test result (if testID is NULL, no result object is provided in the plottingData list)
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.
This is a great start! I've made some initial suggested changes. You can either accept them here on GitHub, or you can make the changes locally, add/commit the changes, and then push to GitHub. This will automatically update the PR.
@curadomr After you address my review comments, the next steps will be adding documentation and tests. For the documentation, start by running |
Co-authored-by: John Blischak <jdblischak@gmail.com>
Co-authored-by: John Blischak <jdblischak@gmail.com>
Co-authored-by: John Blischak <jdblischak@gmail.com>
@curadomr Now that you applied the suggestions I made, make sure you pull these changes to your local copy before you start updating the documentation:
|
- devtools::documentation() - manual entry for test results for getPlottingData
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.
Suggestions on testID default were implemented/accepted. Furthermore, documentation is modified as suggested (devtools::documentation() and manual entry for getPlottingData result section).
Great. The man pages look good. The next step is adding unit tests. Some resources:
I recommend you start by copy-pasting my existing tests of x <- tinytest::run_test_file("inst/tinytest/testPlot.R") You can ignore the failing Ubuntu job. It's failing due to some puzzling GitHub Actions behavior where it has applied some but not all of my recent changes to the build steps. |
- Adding section in tinytest file testPlot.R for the testID implementation
Just added the changes in testPlot.R for the tinytest. On my side, all tests went well following your suggested command: x <- tinytest::run_test_file("inst/tinytest/testPlot.R") |
Tests look good! Last step is to update the vignettes:
|
Please let me know if the modified vignettes suffice for informing the user adequately. |
Thanks @curadomr! 🎉 To update your local copy and fork, please run the following in the terminal:
|