spring-projects / spring-projects/spring-data-jpa
Refine DTO projection rewrite in favor of JPA 4.0's revised implicit DTO mapping
Open
Nobody has claimed this yet.
theme: JPA-4.0
type: enhancement
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
JPA 4.0 brings:
record Summary(String title, String isbn, LocalDate date) {}
select title, isbn, pubDate
from Book
where title like = ?1 and pubDate > ?2
that isn't limited to Records and so we can remove our DTO projection rewrite functionality, or at least, refine it (see also #3929)
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 reading the JPA 4.0 implicit DTO mapping example in this issue and the related discussion in #3929. Inspect the existing DTO projection rewrite functionality, then determine whether it should be removed or refined; done means the chosen approach aligns with the revised mapping behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100