Skip to content

Manuals generated by bioconductor includes internal functions #440

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

Open
oganm opened this issue Feb 19, 2025 · 3 comments
Open

Manuals generated by bioconductor includes internal functions #440

oganm opened this issue Feb 19, 2025 · 3 comments
Assignees

Comments

@oganm
Copy link

oganm commented Feb 19, 2025

This was discussed in the bioc-devel mailing list this month under "Excluding internal functions from package manual".

I was trying to find a way to exclude documenting package internals in the reference files created by bioconductor and was told that R CMD check that bioconductor runs in the build procedure deliberately (?) runs Rd2pdf with --internals option. I am unsure if this behaviour is actually desirable or just an artefact of history but it does cause quite a bit of clutter in the reference pdfs if one elects to document internal functions and it would be nice to have a way not having that.

In contrast, reference pdfs built by CRAN does not include internal functions.

@hpages
Copy link
Contributor

hpages commented Feb 19, 2025

See https://stat.ethz.ch/pipermail/bioc-devel/2025-February/020835.html for my attempt at describing what's going on.

@oganm
Copy link
Author

oganm commented Apr 1, 2025

I should add that one reason we document internal functions, apart from ease of development is inheritance. We have several functions that use the same internal functions to process an output. To avoid keeping multiple copies of the same information that we'd have to manually update, we inherit the return documentation from these internal functions which would make it quite disruptive to remove internal documentation

@jwokaty
Copy link
Collaborator

jwokaty commented Apr 1, 2025

@oganm Thanks for your comment and opening this issue. I plan to address it but may not get to it until after the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants