Suggestion: expand the capability to include `.data$` in tidyverse pipes
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 146
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Currently doing a build check produces lots of no visible binding for global variable [x]. Many of these are bare, unquoted column names in tidyverse pipe chains (see https://www.r-bloggers.com/2019/08/no-visible-binding-for-global-variable/), for instance:
mtcars %>%
mutate(cyl = cyl *2)
This will produce a build check warning of no visible binding for global variable 'cyl'.
The solution to avoid this is:
mtcars %>%
mutate(.data$cyl = .data$cyl *2)
I realize this is a bit more difficult ot determine where to put .data$, but it would be a nice feature.
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
The issue names no files, tests, or entry points. Start by reviewing prefixer's existing namespace-prefixing behavior and the tidyverse pipe examples described here, then determine how bare column names would be identified and where .data$ could be inserted. Done means the supported cases are defined, covered by focused tests, and no longer produce the reported build-check warnings.
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
- Needs clarification
- Newbie friendliness
- 30/100