The maven documentation was missing a few option, a couple of option properties, and was inconsistent regarding selective generation for apis an models. This adds properties and options where appropriate and updates the docs. All options in the README have been reordered to match property declaration order in CodegenMojo, hopefully making it easier for maintainers to recognized when there are docs missing or out of date.
This also slightly refactors the code in CodegenMojo to reduce the
cyclomatic complexity of the execute method.
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.
cc @OpenAPITools/generator-core-team @shybovycha
closes #4938
closes #4937
@shybovycha I hope this documentation update helps make it more clear how to use these properties without potential breaking changes and without using additionalProperties as a fallback as you've proposed in your PR.