Created by: Zomzog
This fix #13830 (closed)
The idea behind the PR is to allow more control to the user for selecting the generation. Currently, we can generate only some models by names. But here we can generate all the models without generating the API.
The code is quite weird because I've kept the initial behaviors. So the behavior changes only if the new properties are used.
If the change is OK I can try to update Gradle and maven plugins to use them.
Ping of the core team because it's a global behavior @wing328 @jimschubert @cbornet @jmini @etherealjoy@spacether
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master(6.1.0) (minor release - breaking changes with fallbacks),7.0.x(breaking changes without fallbacks) -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.