.github/ISSUE_TEMPLATE/feature_request.md

In USEPA/TADA: EPA TADA (Tools for Automated Data Analysis) R Package

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' editor_options: markdown: wrap: 72

Is your feature request related to a problem? Please describe:

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like:

A clear and concise description of what you want to happen. If possible, include an example of how you would like to see the code work:

library(TADA)
super_cool_feature(x, y)

Describe alternatives you've considered:

A clear and concise description of any alternative solutions or features you've considered.

Additional context:

Add any other context or screenshots about the feature request here.

Reminders for TADA contributors addressing this issue:

New features and/or edits should include all the following work:

• [ ] Create or edit the function/code.

• [ ] Document all code using line/inline and/or multi-line/block comments to describe what is does.

• [ ] Create or edit tests in tests/testthat folder to help prevent and/or troubleshoot potential future issues.

• [ ] Create or edit the function documentation. Include working examples.

• [ ] Update or add the new functionality to the appropriate vignette (or create new one).

• [ ] If function/code edits made as part of this issue impact other functions in the package or functionality in the shiny app, ensure those are updated as well.

• [ ] Run TADA_UpdateAllRefs(), TADA_UpdateExampleData(), styler::style_pkg(), devtools::document(), and devtools::check() and address any new notes or issues before creating a pull request.

• [ ] Run more robust check for releases: devtools::check(manual = TRUE, remote = TRUE, incoming = TRUE)

USEPA/TADA documentation built on April 12, 2025, 1:47 p.m.