spring-projects / spring-projects/spring-data-commons
Introduce ResolvablePropertyPath
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 838
- Forks
- 730
- PR merge metrics
- No merged PRs in 30d
Description
The current property path resolution is fixed in its behaviour providing litte to no flexibility for consuming modules.
Sometimes it is desirable to be able to walk a path partially up to the point that was resolvable or be able to ask the object if the path exits and can be resolved without having to deal with the current PropertyReferenceException.
The path factory would also be able to cache ResolvablePropertyPath instances even if they cannot be resolved as a whole, which is currently only possible for fully resolvable paths.
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 current property path resolution, the path factory, and PropertyReferenceException handling in the repository. Define the ResolvablePropertyPath API around partial resolution, checking whether a path exists, and caching paths that are not fully resolvable; done means these behaviors are supported without requiring consumers to handle the current exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100