You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is there any plans on support annotations (e.g. @Property) at the member variable instead of getter/setters (similar to JPA)? This would provide a much better overall experience in Java as well as Kotlin.
Thanks,
The text was updated successfully, but these errors were encountered:
That would change the architecture significantly. you would have to pull
out objects, modify them, then submit them back to get updated (like you do
in jpa). In our current model when you call the setter it calls back to the
underlying tinkerpop object.
On Wed, Jun 27, 2018 at 1:18 PM EYL Francois ***@***.***> wrote:
Hi guys,
is there any plans on support annotations (e.g. @Property
<https://github.com/property>) at the member variable instead of
getter/setters (similar to JPA)? This would provide a much better overall
experience in Java as well as Kotlin.
Thanks,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#51>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5JAnhJdrRxn0eaNgIn3yi_81T1QRv3ks5uA2oRgaJpZM4U5hl->
.
Hi guys,
is there any plans on support annotations (e.g. @Property) at the member variable instead of getter/setters (similar to JPA)? This would provide a much better overall experience in Java as well as Kotlin.
Thanks,
The text was updated successfully, but these errors were encountered: