r-devel / cran-cookbook

Problem and solution documentation for common CRAN issues
http://contributor.r-project.org/cran-cookbook/
44 stars 1 forks source link

Best practices for extra CRAN checks? #21

Open dgkf opened 3 months ago

dgkf commented 3 months ago

Hi chefs of the CRAN cookbook :woman_cook:

I've often wondered what the best path would be for distributing developer-side extra CRAN checks.

I'm frequently guilty of not documenting all return types or including examples in non-exported functions and I feel sorry for the CRAN folks that frequently have to remind me to satisfy these easily satisfied checks.

For my own common pitfalls I have a little script I run on my side (when I remember) to try to get ahead of this, but I'm wondering if there's a better way to build up a library of additional checks.

Any ideas on how we can make it easier to satisfy the easily automated checks?

llrs commented 3 months ago

While I am not a "chef" of this book, I am not sure this is the place to discuss this. The goal of this CRANcookbook is to document common problems already existing when submitting to CRAN: your example of missing return value of the documentation is already included. A better suited place might have been the R repository working group, until it changed goals...

However, I'll start answering from the last one to the first question.

I hope this helps.