Break R functions into multiple files
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We shall break https://github.com/Merck/mmrm/blob/main/R/util_fn.R into smaller files.
The general rule of thumb is to have one file per R function. The filename and function name shall matches.
Sometimes, we also group some small functions in one files. For example
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing R/util_fn.R and inventorying the functions it contains. Compare the organization with pkglite's R/utils.R example, then split functions into appropriately named R files, grouping only small related functions where justified. Done means the utility code follows the stated one-function-per-file convention without changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100