spring-projects / spring-projects/spring-data-rest
Create an extension mechanism that lets users tie into process of turning a domain object into a representation object [DATAREST-7]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 958
- Forks
- 568
- PR merge metrics
- No merged PRs in 30d
Description
Jon Brisbin opened DATAREST-7 and commented
We need to be able to inspect, validate, or alter the representation of the object going back to the client. One way to do this is to provide a system of annotations that users can put on their classes that the exporter will recognize and call when that lifecycle event is triggered. The exporter could invoke a handler method of a class annotated with a @ResourceHandler annotation and specifying the domain class it's a handler for
Affects: 1.0 - M1
2 votes, 2 watchers
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 locating the exporter process that turns a domain object into a representation and identify where a @ResourceHandler-based handler could be invoked. Review how handler methods would be associated with their domain class, then define the extension behavior for inspecting, validating, or altering the representation before it is returned to the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100