Check and annotate packages across an entire project
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 103
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We often have projects where packages are loaded in a separate script or in a 'set-up' type script and used across other scripts throughout the project.
It would be good to be able to check and annotate across a whole project, some interesting notes I would like to see are:
- `# Not used`
- `# Used in script x, y, z ...`
- `# ... (Also loaded in script x)`
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified in the issue. First trace how annotater currently finds package loads, then define project-wide traversal and annotation expectations for packages loaded in one script and used in others; done means those cases are reported consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100