(Automated) pkgcheck report for USEPA/RAQSAPI
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 26
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Checks for RAQSAPI (v2.0.6)
git hash: 1baf0874
NOTE: R package is in the '.' sub-directory
- ✔️ Package is already on CRAN.
- ✔️ has a 'contributing' file.
- ✔️ uses 'roxygen2'.
- ✔️ 'DESCRIPTION' has a URL field.
- ✔️ 'DESCRIPTION' has a BugReports field.
- ✔️ Package has at least one HTML vignette
- ✔️ All functions have examples.
- ✔️ Repository has a website
- ✖️ Package fails continuous integration checks.
- ✖️ Package coverage failed
- ✖️ R CMD check found 1 error.
- ✔️ R CMD check found no warnings.
- 👀 Some goodpractice linters failed.
- 👀 Examples should not use
\dontrun{}unless really necessary.
Important: All failing checks above must be addressed prior to proceeding
(Checks marked with 👀 may be optionally addressed.)
Package License: MIT + file LICENSE
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 reproducing the reported continuous integration, coverage, and R CMD check failures for the R package in the repository's '.' sub-directory. Inspect the failing check output and goodpractice results to identify the affected files; done means the required checks pass, while the eyes-marked linter findings are optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100