Documentation: Increase visibility of results using print statements
Open
@kodesiba is already working on this.
Since Jan 16, 2025.
Assessment
This issue has not been assessed yet.
Description
documentation
- Vignettes should have clearer documentation on capturing results and best practice.
- Different types of outputs that R creates and how R/logrx grabs them
- Dominant language
- HTML
- Stars
- 49
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from pharmaverse/logrx
-
Hackathon: Tier 1 Pharmaverse Hackathon
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pharmaverse/logrx#309 ·
-
Hackathon: Tier 1 Pharmaverse Hackathon
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
pharmaverse/logrx#308 ·
-
Update logrx adsl examplePossibly taken @umayal-a claimed this 6 days ago. OpenHackathon: Tier 2 Pharmaverse Hackathon
Difficulty 4/5 3-5 days Newbie friendliness 42/100
pharmaverse/logrx#311 · 5 comments · 1 assignee ·
-
Fix Version BumpOpenHackathon: Tier 2 Pharmaverse Hackathon
Difficulty 3/5 1-2 days Newbie friendliness 35/100
pharmaverse/logrx#310 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
pharmaverse/logrx#307 ·