grantmcdermott / grantmcdermott/tinyplot
Inconsistent use of `FUN` and `fun`
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 427
- Forks
- 25
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 28
Description
... in the type-level arguments.
FUN:
type_barplot()type_area()
vs.
fun:
type_summary()type_function()type_hexbin()
Enforcing one standard will obviously be a breaking change. Aliasing is probably the least painful thing we can do from a user perspective.
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
Locate the type-level argument definitions for type_barplot(), type_area(), type_summary(), type_function(), and type_hexbin(), then compare how FUN and fun are exposed. Check existing tests or examples for these functions before choosing the compatibility-preserving naming approach. Done means one consistent user-facing convention without breaking the existing argument names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100