-
Notifications
You must be signed in to change notification settings - Fork 682
Introduce PersistentProperty.isReadable
#2915
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.
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
Comments
PersistentProperty.isReadable
for easier downstream usage
PersistentProperty.isReadable
for easier downstream usagePersistentProperty.isReadable
mp911de
added a commit
that referenced
this issue
Aug 28, 2023
isReadable reports whether a property can be read through PersistentPropertyAccessor, by either using property access through setters, a wither, Kotlin Copy method or by accessing the field directly. Closes #2915
mp911de
added a commit
that referenced
this issue
Aug 28, 2023
isReadable reports whether a property can be read through PersistentPropertyAccessor, by either using property access through setters, a wither, Kotlin Copy method or by accessing the field directly. Closes #2915
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on spring-projects/spring-data-mongodb#4485, we should introduce a
isReadable
flag for easier downstream usage of truly immutable properties. The immutable flag just expresses immutability on the instance but requires checks for withers and Kotlin copy methods for creating a new instance. That isn't handy for values of Kotlin data classes (properties of a Kotlin data class that cannot be set viacopy
).The text was updated successfully, but these errors were encountered: