spring-projects / spring-projects/spring-data-rest
ResourceProcessors do not get invoked anymore [DATAREST-61]
Open
Nobody has claimed this yet.
type: bug
- Dominant language
- Java
- Stars
- 958
- Forks
- 568
- PR merge metrics
- No merged PRs in 30d
Description
Oliver Drotbohm opened DATAREST-61 and commented
A registered ResourceProcessor<Person> does not get invoked anymore. The reason seems to be that ResourceProcessorHandlerMethodReturnValueHandler.isValueTypeMatch(…) has an ….equals(…) check where it should be an ….isAssignableForm(…)
No further details from DATAREST-61
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 in ResourceProcessorHandlerMethodReturnValueHandler.isValueTypeMatch(…) and inspect the type comparison for a registered ResourceProcessor. Done means an assignable ResourceProcessor is matched and invoked rather than being skipped by the equality check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100