Fixing bug disabling JSON inline serialization for non managed types #111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
…ties/types (i.e exported=false in corresponding Repository)
| The same change was already done via 0667e0b on DATAREST-200. |
| @gregturn @olivergierke this issue is still present in latest version i.e., spring-data-rest version 2.0.0.RC1 |
| See DATACMNS-250 for further development. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Hi,
In previous versions, I used to annotate some JPA repositories with exported=false in order to avoid Link creation in an entity. In such case, these entities was just serialized through standard JSON serialization like { "property":"value"}
The following patch is bypassing an optimization which is actually breaking this comportment.
Thanks a lot for your amazing work done so far !
Romain