openapi-generator

openapi-generator copied to clipboard

Cleaned up cargo clippy warnings rather than explicitly allowing them.

@frol @farcaller @richardwhiuk @paladinzh

PR checklist

• [x] Read the contribution guidelines.
• [x] 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.
• [x] Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  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 ./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH.
• [x] File the PR against the correct branch: master (6.1.0) (minor release - breaking changes with fallbacks), 7.0.x (breaking changes without fallbacks)
• [x] If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

can you please regenerate the samples?

can you please regenerate the samples?

Any special flags I should be passing? Running ./bin/generate-samples.sh results with all files in samples/openapi3/client/3_0_3_unit_test/python-experimental/test/ being removed. Just want to verify before pushing a bunch of deletes that shouldn't have occurred.

No worry. I'll update the samples after the merge.

Tested locally with updated samples and the result is good.