Skip to content

Deprecate KPropertyPath in favor of Spring Data Common's KPropertyPath [DATAMONGO-2662] #3515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
spring-projects-issues opened this issue Nov 26, 2020 · 0 comments
Closed

Deprecate KPropertyPath in favor of Spring Data Common's KPropertyPath [DATAMONGO-2662] #3515

spring-projects-issues opened this issue Nov 26, 2020 · 0 comments
Assignees
@christophstrobl
Labels
in: kotlin Kotlin support type: task A general task
Milestone
3.2 M2 (2021.0.0)

Comments

@spring-projects-issues
Copy link

spring-projects-issues commented Nov 26, 2020 •
edited by christophstrobl
Loading

Mark Paluch opened DATAMONGO-2662 and commented

Issue Links:
@spring-projects-issues spring-projects-issues added in: kotlin Kotlin support type: task A general task labels Dec 30, 2020
christophstrobl added a commit that referenced this issue Jan 11, 2021
@christophstrobl
GH-3515 - Prepare issue branch.
3887cf4
christophstrobl added a commit that referenced this issue Jan 11, 2021
@christophstrobl
GH-3515 - Deprecate KPropertyPath in favor of Spring Data Common's KP…
67b16cf 
…ropertyPath.
@christophstrobl christophstrobl mentioned this issue Jan 11, 2021
Closed
christophstrobl pushed a commit to spring-projects/spring-data-commons that referenced this issue Jan 12, 2021
@mp911de @christophstrobl
DATACMNS-1835 - Provide Type-safe Kotlin query extension.
2bf5e53 
We now provide a KProperty extension leveraging KProperty references to express a property path. Using Kotlin property references (such as Author::name that translates to `book` or Book::author / Author.name translating to `book.author`) is refactoring-safe as the property expressions are part of the Kotlin language. We render KPropertyPath using the same semantics as our PropertyPath so that store-specific modules can leverage either property paths or accept KProperty directly.

In contrast to the previous implementation, KPropertyPath is private and the rendering function was renamed to toDotPath to align with PropertyPath.toDotPath.

Related ticket: DATAMONGO-2138 (spring-projects/spring-data-mongodb#3515)
Original Pull Request: #478
Closes: #2250
@christophstrobl christophstrobl added this to the 3.2 M2 (2021.0.0) milestone Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@christophstrobl christophstrobl

Labels
in: kotlin Kotlin support type: task A general task
Projects
None yet
Milestone
3.2 M2 (2021.0.0)
3 participants
@mp911de @christophstrobl @spring-projects-issues