Closed emmanuelmathot closed 3 months ago
thanks for the PR
cc @linxGnu
Basically LGTM. However, because it touches the template, could you please run Integration Test @emmanuelmathot
If the integration tests do not contains response range, please add update/add new api endpoint. Please refer to this PR as an example: https://github.com/OpenAPITools/openapi-generator/pull/18362
@emmanuelmathot please note that axum uses different test cases.
./bin/generate-samples.sh ./bin/configs/manual/*.yaml
mvn integration-test -f samples/server/petstore/rust-axum/pom.xml
As you can see, samples are generated under ./bin/configs/manual
instead
merged https://github.com/OpenAPITools/openapi-generator/pull/18938 (follow up PR) to update samples with cargo fmt
This PR adds support for response ranges in rust-axum server, as defined in section 4.8.16.2 of the spec.
PR checklist
(For Windows users, please run the script in Git BASH) 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*
. IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.master
(upcoming 7.6.0 minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)