Suggestion: Refactor GuestbookResponseService
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Suggestion While working on https://github.com/IQSS/dataverse/issues/11740 it became apparent that the GuestbookResponseService was designed to work best with JSF. I propose a refactor to make this service work with SPA in mind.
What kind of user is the suggestion intended for? ALL
What inspired this idea? Refactoring Access to not be heavily tied to Session Authentication
What existing behavior do you want changed? Make more inclusive for SPA
Any brand new behavior do you want to add to Dataverse?
Any open or closed issues related to this suggestion? https://github.com/IQSS/dataverse/pull/11844
Are you thinking about creating a pull request for this issue?
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 reviewing GuestbookResponseService and the context in issue #11740, then read pull request #11844 for related Access and authentication work. Clarify the SPA use cases and define the service behavior that would count as complete before planning the refactor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100