`cran-extrachecks`: clarify rules on exported generic functions

Open Beginner friendly
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
r
Domain
documentation

Research direction

Edit r-lib/cran-extrachecks/SKILL.md. Start by reading the rules for exported functions and the CRAN checks for @return and @examples, then clarify the exception for exported S3 generics such as print.class_name when only @export is present and no .Rd is created. Done means the skill clearly explains when those tags are not required.

Written by the indexing model from the issue text.

Description

Have been trying out the CRAN submission skill and it has done great; much better than my earlier attempt to do something similar.

The one issue I've run into is that it flags exported S3 generics, e.g. print.class_name, as needing @return and @examples, even if there is no Roxygen documentation except #' @export.
Seems like it might be good to edit the skill to explain this exception to the CRAN rules (no .Rd is actually created here)

Dominant language
R
Stars
517
Forks
53
Avg merge
17m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from posit-dev/skills

All issues in posit-dev/skills

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.