Created by: shybovycha
Introduction
There is one quite nifty but undocumented option, apis, which could be set in system properties. It defines which API groups should be generated. Given the undocumented internal behavior of grouping all operations by tags, this gives an easy way to migrate existing projects to Open-API with minimal changes by automatically generating API definitions and then generating API interfaces with operations automatically grouped according to the existing endpoints.
Hence I am creating a few PRs (#4937, #4938, #4939) addressing this hidden gem of openapi-generator.
This change
I could not really find a good way to pass values through SystemProperties when using the maven plugin. Hence it is pretty much impossible from my point of view to set the apis property, I think that it could also be passed through the additionalProperties option.
Also, see the other PR ( #4938 ) which fixes a bug in parsing the list options in additionalProperties.
Does not seem like a breaking change, hence targeting master.
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.3.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.