Make sure name makes sense
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue names no files or tests. Start with the repository description and current command-line behavior, then assess whether the project name fits running R scripts in a persisted environment; done means an agreed name that makes sense in that context.
Written by the indexing model from the issue text.
Description
We're not performing "method dispatch" or anyhing like that. Need to make sure the project name makes sense in the context of what it's doing. I just pulled it out of the air and I'm a bit concerned it doesn't actually work.
- Dominant language
- R
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 dmarx/dispatchr
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Switch to POST?Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Add authenticationOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Component: R
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
bug pixi-build-r
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prefix-dev/pixi#7229 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rstudio/reticulate#1933 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100