- cleanup old docs across all dart generators
- regenerate all tests
- cleanup .gitignore
- minor formatting improvements in dart-dio
- unified integration-test layout for dart/dart-dio generators
- add generation and integration-tests for OAS3 petstore to dart/dart-dio
- add generation and integration-tests for OAS3 petstore-with-fake-api to dart/dart-dio
Explicitly not adding the new integration tests for petstore-with-fake-api to the master POM. They do not work but having them allows for quickly iterating on open issues without breaking existing basic OAS2/OAS3 petstore examples. Instead they should be run manually until everything is fixed.
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. -
If contributing template-only or documentation-only changes which will change sample output, build the project beforehand. -
Run the shell script ./bin/generate-samples.shto update all Petstore samples related to your fix. 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./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 -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.
TODO:
-
Verify new inline objects are correct, they seem to be unused -
Fix compile errors in dart regarding File/MultipartFile -
Fix tests for POST/PUT operations that now return 200with content