Consider dropping the dplyr dependency by registering the methods at load time
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by examining how the package currently depends on dplyr and how its methods are registered. Compare that approach with the load-time registration used by arrow; done means the methods register at load time and the dplyr dependency can be removed.
Written by the indexing model from the issue text.
Description
Looks good to me. Eventually we also should probably consider dropping the dplyr dependency by registering the methods at load time like arrow does. Thanks for this.
Originally posted by @boshek in https://github.com/bcgov/bcdata/pull/300#issuecomment-1174588331
- Dominant language
- R
- Stars
- 87
- Forks
- 14
- 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 bcgov/bcdata
-
running air in CI Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
considering
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
considering enhancement wfs
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
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