Updated swagger-core to version 1.6.1 to support 'parseValue' in 'extensions' #877
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.
In version 1.6.1
swagger-core
(andswagger-annotations
) added support for theparseValue
property as part of the@ExtensionProperty
annotation.If
parseValue
istrue
the provided value is treated as json and it's parsed into the generated OpenAPI file as a nested object or an array (instead of as a string).In this PR I upgraded the
swagger-core
library from1.5.21
to1.6.1
and updated the relevant tests (same as in https://github.com/kongchen/swagger-maven-plugin/pull/582/files).I also upgraded other libraries to try to make
mvn install
work (but it doesn't) and run the tests in Intellij (that works), so these changes might not be needed ifmvn install
works in the CI.I was able to make
mvn install -DskipTests
work with the additional libraries upgrades only if I manually disable thecheck-java16-sun
execution (inanimal-sniffer-maven-plugin
).Please let me know if you want to keep these additional upgrades or remove them.