IQSS / IQSS/dataverse-frontend
For Dataset Page, handle unauthorized response from the API differently from version not found.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
In the SPA, if an unauthenticated user tries to access the draft version of a dataset, the page redirects to the latest published version with a message that the the Draft version wasn't found, for example:
In JSF, instead of showing the latest version, the user is redirected to the login page. We don't have login built into the SPA yet, so maybe we can show an unauthorized page? Or keep the behavior as is, and add the logic to redirect to login when it is available.
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 at the SPA Dataset Page handling for API responses when an unauthenticated user requests a draft version, and compare it with the described JSF behavior. Resolve whether the result should be an unauthorized page or remain the current behavior pending login support. Done means unauthorized access is no longer presented as a missing draft version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100