jamesplease / jamesplease/api-pls
Updates to errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The following common error situations should have good errors:
1. foreign key constraint error (related resource does not exist)
2. id in URL does not match body.data.id
3. attempting to null a non-null field
4. foreign key constraint error: one-to-one relationship where it would make the value not unique
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 locating the JavaScript backend's error handling for the four situations listed: foreign-key failures, mismatched URL and body IDs, nulling non-null fields, and one-to-one uniqueness violations. Review how current errors are generated, then verify that each situation produces a clear, appropriate error response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgresql
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100