The-Strategy-Unit / The-Strategy-Unit/data_science
Error handling in functions
Open
Nobody has claimed this yet.
session: C&C ☕
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
- Principles of error handling
- Doing it quickly - When you have little time
- Doing things properly(?) with purrr::safely() or purrr::possibly()
- Handling the output of purrr::safely()
- Sending messages back to the user (and being able to turn them off)
- What to do when you can’t resolve errors
- Could include the classics first, like tryCatch(), if and stop(), etc (Matt)
- Nice error reporting with {cli} (Matt)
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
No file, notebook, or documentation entry point is named. Start by locating the project’s existing R teaching materials and reviewing how error handling is currently covered. Done means adding an agreed section covering the listed topics, including tryCatch(), purrr::safely(), purrr::possibly(), user messages, and cli reporting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100