spring-projects / spring-projects/spring-data-commons
Introduce convenience constructor to `MappingException` accepting an entity/property
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 838
- Forks
- 730
- PR merge metrics
- No merged PRs in 30d
Description
Message creation for MappingException is subject to each place that raises an exception hence we don't have a consistent style how mapping exceptions report offending entities and properties. We should have some means to consistently generate the part which relates to the offending entity/property.
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 MappingException and reviewing its existing constructors and the places that raise mapping exceptions. Compare how offending entities and properties are currently reported, then make the constructor usage consistent across those callers and verify that the resulting messages include the relevant entity and property details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100