Create validateAcuteChronic
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
No file or test is named. Search the repository for existing validation functions and their tests to follow the project’s conventions, then define the expected behavior for the Acute/Chronic field: accept A, C, and NA, while rejecting values such as acute and chronic.
Written by the indexing model from the issue text.
Description
The allowable values should be 'A', 'C', or NA to ensure consistent format and prevent accidental user entry for instance if they were to enter 'acute' or 'chronic' which does not follow the format.
- Dominant language
- R
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from USEPA/TADACommunityHub
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
USEPA/TADACommunityHub#16 ·
-
collaborator
Difficulty 4/5 3-5 days Newbie friendliness 48/100
USEPA/TADACommunityHub#41 ·
-
dependencies documentation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
USEPA/TADACommunityHub#35 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
USEPA/TADACommunityHub#24 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
USEPA/TADACommunityHub#23 ·
All issues in USEPA/TADACommunityHub
Similar issues
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
function:write_dwc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
beginners blocker
Difficulty 2/5 1-3 hours Newbie friendliness 78/100