IQSS / IQSS/dataverse-frontend
Integrate the js-dataverse not found error
Open
Nobody has claimed this yet.
pm.GREI-d-2.7.1
pm.GREI-d-2.7.2
Size: 30
Waiting
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
Identify the new NotFoundError in the catch block of the use case calls and handle it accordingly.
What kind of user is the feature intended for?
This feature is intended for all users.
What inspired the request?
- https://github.com/IQSS/dataverse-client-javascript/issues/142
- https://github.com/IQSS/dataverse-frontend/pull/352#discussion_r1549779417
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
Integrate the js-dataverse not found error
Any open or closed issues related to this feature request?
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 reading js-dataverse issue 142 and locating the use case call catch blocks in this repository. Determine how the new NotFoundError should be handled there, then verify that the not-found behavior is integrated for all relevant calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100