tidymodels / tidymodels/important
passthrough calls to errors
Open
Nobody has claimed this yet.
tidy-dev-day :nerd_face:
- Dominant language
- R
- Stars
- 19
- Forks
- 1
- Avg merge
- 2h 6m
- Merged PRs (30d)
- 1
Description
"call threading" is when we pass an object that reflects the call that we want the user to see when there is an error (instead of where the error might actually occur).
In brulee, there are a few that show the call from the lower-level function.
example pr: tidymodels/hardhat#275
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
Start by reviewing the brulee call-threading cases described in the issue and the example tidymodels/hardhat#275. No files or tests are named; done means errors show the intended user-facing call rather than the lower-level function where the error occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100