IQSS / IQSS/dataverse-client-javascript
Create the NotFoundError
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 11
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 1
Description
Overview of the Feature Request
For now any error returned by the API in a read operation returns a ReadError, which includes the message with the HTTP error code as a very simple string, but we can define a new NotFoundError that extends ReadError also including more refined data. This way we can safely identify a not found error within the block catch of the promise, and carry out the necessary actions in the SPA.
What Inspired the Request?
What Existing Behavior Do You Want Changed?
Error handling
Any Brand New Behavior Do You Want to Add to js-dataverse?
New not found error
Any Open or Closed Issues Related to This Feature Request?
No
Contributor guide
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 tracing the existing ReadError implementation and read-operation error handling in js-dataverse. Determine where API not-found responses are converted into errors and what refined data is available there. Done means a distinct NotFoundError can be identified in a promise catch while retaining the existing ReadError behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100