-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add examples to exported functions #157
Comments
as_latent_individual
I agree that we should add examples! Thanks for the suggestion, and for having a look at the package in these early stages more generally |
It's a pleasure. It's coming along nicely. |
Note to self that this is a good one to work on soon. |
The first step here is to make certain data objects available. Perhaps this could also be used to simplify things being available within tests. |
@seabbs is this something we might want to consider as a part of public release? |
You'll need to do it if submitting to CRAN. It's a requirement. |
Thanks @jamesmbaazam. The plan we have is an inital "public" release on GitHub / R Universe next week. (After a temporary "internal" release tomorrow.) So I think CRAN is a bit longer into the future. Nonetheless I think this is a useful feature (especially for new users to the package) and it'd be nice to have sooner rather than later. |
PRs welcome if it's something you might feel up for tackling as part of your work! |
Mostly done in #513 |
Im going to close this in favour of more targetted issues at remaining gaps |
The key exported functions could benefit from having examples. I've noted
as_latent_individual()
, which tends to be called as the first step beforeepidist()
. The latter,epidist()
, also could benefit from the same suggestion.The text was updated successfully, but these errors were encountered: