Fix and update swagger client generation #384
Merged
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
|
Sorry, I'm currently a little busy, I'll review/test this next week. |
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.
Hey again,
I wanted to tackle #372 but it showed the following error:
It seems that after years of warnings the time of updating the client has come.
So I generated a new client version (including Java 11 instead of Java 7). It needed some adjustments (see new README instructions and updated gradle code), but it works now.
I've used the newest available version of Swagger Codegen.
What do you think? There shouldn't be breaking changes in the code itself, right?
I will test the new version some more, but for now everything seems to be working.