shift-org / shift-org/shift-docs
Improve calendar API error handling
Open
Nobody has claimed this yet.
API
backend
enhancement
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Once the current API behavior is documented (#131), we should add and improve error handling where needed.
Look for cases where errors do exist but could be more specific, and places where errors are currently unhandled.
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 current API behavior documented in issue #131, then locate the calendar API paths where errors are handled or missing. Done means the needed error cases are identified and handled with specific responses, but the issue does not name particular files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100