Use OpenAPI tag names to generage Java API interfaces #20
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.
Add the
<useTags>true</useTags>
configuration option to theopenapi-generator-maven-plugin
, so it generates Java API interfaces based on the tags of each operation instead of using the URI paths.This leads to the following refactoring of classes:
CollectionsApi
->DataApi
DefaultApi
->CapabilitiesApi
Additionally, some methods from the
DataApi
are moved to theCapabilitiesApi
, as they're annotated with theCapabilities
tag in the OpenAPI definition.