Created by: AlexanderEggers
Fixes #4651 (closed).
- consumes the OpenApi 3.0 nullable field definition; if defined, even required fields will be nullable.
- required-nullable fields won't have a default value. The field is still required to exist - only it's value is null.
- added new kotlin-client sample to show the nullable-field changes
- in the model "Pet" the field "name" is now nullable. In the yaml it is defined as a required nullable field.
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.
@jimschubert (2017/09)