craig-shenton rapR-package-template issues

craig-shenton / rapR-package-template

An R/Quarto package template based on NHS Digital's python version that can be adapted for RAP projects.

https://github.com/NHSDigital/rap-community-of-practice

MIT License

8 stars 1 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

What is the correct static branching naming strategy for targets?

#23 craig-shenton opened 1 year ago
0
can only build Quarto reports using targets if `my_R_package/` is root folder

#22 craig-shenton opened 1 year ago
0
Does testthat test need to be in a folder called "testthat"

#21 craig-shenton opened 1 year ago
0
Possible to run _targets.R script from utilities folder?

#2 craig-shenton closed 1 year ago
1
Best way to setup an R virtual environment?

#1 craig-shenton closed 1 year ago
2
Code is fully packaged

#3 craig-shenton opened 1 year ago
0
Data is handled and output in a Tidy data format

#7 craig-shenton opened 1 year ago
4
Logs are automatically recorded by the pipeline to ensure outputs are as expected

#15 craig-shenton opened 1 year ago
0
Repository includes package dependency information

#16 craig-shenton opened 1 year ago
0
Pipeline includes a testing framework (unit tests, back tests)

#17 craig-shenton opened 1 year ago
0
Code adheres to agreed coding standards (e.g., PEP8)

#20 craig-shenton opened 1 year ago
0
Repository automatically runs tests etc. via CI/CD or a different integration/deployment tool e.g. GitHub Actions

#4 craig-shenton opened 1 year ago
0
Process runs based on event-based triggers (e.g., new data in database) or on a schedule

#5 craig-shenton opened 1 year ago
0
Changes to the RAP are clearly signposted. E.g. a changelog in the package, releases etc. (See gov.uk info on Semantic Versioning)

#6 craig-shenton opened 1 year ago
0
Reusable functions and/or classes are used where appropriate

#14 craig-shenton opened 1 year ago
0
Code is well-organised following standard directory format

#13 craig-shenton opened 1 year ago
0
Outputs are produced by code with minimal manual intervention

#12 craig-shenton opened 1 year ago
2
Code is published in the open and linked to & from accompanying publication (if relevant)

#19 craig-shenton opened 1 year ago
0
Code has been peer reviewed (i.e., use PRs and code reviews)

#11 craig-shenton opened 1 year ago
0
Code is well-documented including user guidance, explanation of code structure & methodology and docstrings for functions

#18 craig-shenton opened 1 year ago
0
Repository includes a README.md file (or equivalent) that clearly details steps a user must follow to reproduce the code

#10 craig-shenton opened 1 year ago
0
Code is version controlled (i.e., Git & GitHub)

#9 craig-shenton opened 1 year ago
0
Data produced by code in an open-source language (e.g., Python, R, SQL)

#8 craig-shenton opened 1 year ago
1