fix for spring data rest 3.0.5.RELEASE while maintaining backward com… #2323
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…partibility
What's this PR do/fix?
The current swagger version doesn't work with new version of spring data rest (3.0.5.RELEASE). This pull request fixes that problem while maintaining backward compatibility.
Are there unit tests? If not how should this be manually tested?
No new unit tests required for the changes, the existing unit tests have those.
Any background context you want to provide?
Swagger data rest doesn't work with new spring data rest version 3.0.5.RELEASE due to the fact that new spring version returns java 8 Optional instead of direct object.
What are the relevant issues?
Current Swagger data rest (2.8.0) doesn't work with new spring data rest version 3.0.5.RELEASE