Write Reusable, Composable and Modular R Code
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
This R package seems like it COULD be a very suitable answer to our pacta.* vs worfklow.* conundrum...
It is more or less a "superset" of R packages, that loosen some of the R packages conventions up, and allow modules to be loaded from different directories in the project.
It is in version 1.2.0 which may suggest that the developers believe it to be stable enough for a first release.
I am hesitant to incorporate new/ semi-experimental topics into our standard project structures, but since workflow.*s are a bit of a "wild west" anyway, ¯_(ツ)_/¯ could be interesting.
cc: @AlexAxthelm @cjyetman
Contributor guide
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 the linked box package documentation and the related practices issue #2. Determine whether box addresses the pacta.* versus workflow.* structure and whether it is suitable for the project's standard conventions; done should include a clear decision and defined project-structure guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100