Just rebuilding the samples.
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.
Activity
Appveyor CI tests didn't pass despite restarted several times: https://ci.appveyor.com/project/WilliamCheng/openapi-generator/builds/45014214
Can you please take a look when you've time?
added Client: C-Sharp Enhancement: CI/Test labels
changed milestone to %6.2.1
@wing328 The tests failing also fail for master. @Blackclaws can you take a look? Looks to me like the add pet method should have authentication but there is none. For comparison, the delete pet method does have authentication.
@wing328 The tests failing also fail for master.
did you run the pestore server locally?
https://github.com/OpenAPITools/openapi-generator/wiki/Integration-Tests
appveyor tests passed via https://ci.appveyor.com/project/WilliamCheng/openapi-generator/builds/45081364
