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.
Clear description of my expectations versus reality
With Entities having an IdClass annotation and using other Entities as the id, Javers will use the toString of the id entity and not the id property. This could result in a very long InstanceId.
(See the linked test case for an example)
Steps To Reproduce
I have a **runnable test case ** which isolates the bug and allows Javers Core Team to easily reproduce it. I have pushed this test case to my fork of this repository:
Additional context
With the dehydrate of the composite key values I was able to achieve that the InstanceId to contains only the referenced entities id field and not the toString representation of those entities.
The text was updated successfully, but these errors were encountered:
Clear description of my expectations versus reality
With Entities having an IdClass annotation and using other Entities as the id, Javers will use the toString of the id entity and not the id property. This could result in a very long InstanceId.
(See the linked test case for an example)
Steps To Reproduce
I have a **runnable test case ** which isolates the bug and allows Javers Core Team to easily reproduce it. I have pushed this test case to my fork of this repository:
bala-striva@803d6ae
Javers' Version
5.9.4-master
Additional context
With the dehydrate of the composite key values I was able to achieve that the InstanceId to contains only the referenced entities id field and not the toString representation of those entities.
The text was updated successfully, but these errors were encountered: