-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update function documentation #78
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.
Useful start; seems like assorted minor missing bits
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.
Just a couple small comments, thanks!
Co-authored-by: Carl A. B. Pearson <pearsonca@users.noreply.github.com>
…n>: <description>]
Although this PR wasn't targeting #27, the suggestions and changes have tackled some of the points mentioned in that issue. I've left a comment in #27 that only Thanks for the comments @pearsonca and @sbfnk, let me know if there's anything else to the changed, if not, I'm happy for this to be merged when you're ready. |
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.
I think it's fine as is, but also commented on two minor improvements you might make
This PR addresses #58 & #67.
I've removed duplicated documentation of function arguments and used
@inheritParams
instead.outbreak_model.R
is the main function that documents arguments and other functions that have the same arguments inherit from there.I've added
@return
documentation to exported functions that were previously missing it.Issue #27 could also have been addressed in this PR, but as I'm still getting familiar with the codebase I didn't have many improvements on the general function documentation for now, and will address this in a subsequent PR.