* Remove redundant Rust use statement
* Return errors only for 4xx and 5xx in Rust reqwest
Since 1xx and 3xx are perfectly valid status codes the client might
need to handle.
see: https://docs.rs/reqwest/0.11.0/reqwest/struct.StatusCode.html#method.is_informational
* Regenerate samples
Co-authored-by: Gabriel Féron <feron.gabriel@gmail.com>
* Stronger typing for http errors with Rust client. (#5609).
* Error structure can be parametrized (but is still hardcoded with `serde_json::Value` in generated code).
* Each API method has is own enum of functionnal errors.
* Fix the missing "Debug" derivation for API error enums.
* Generate models for error deserialization.
* Handle several 2xx success models.
* Expose new API objects, required to use the API (params, success, error structs/enums).
Co-authored-by: William Cheng <wing328hk@gmail.com>
This PR includes theses changes:
- Handling "optional" parameters is not optional anymore. Handling an additional parameter for it makes templates more complicated, and IMO, it is not worth it (as discussed in issue, it is an "acceptable" breaking change).
- Optional parameters are handled everywhere: path params, query params, form params... Generated sample code compiles (both hyper and reqwest libraries).
* Add support for the `discriminator` feature of OpenAPI 3, and implement it with `enum` in Rust
* Add all missing explicit `dyn` to trait types to remove warnings
* Add missing re-export for properties that are enum (was missing from #2244).
As we discovered in #3463, there are various bits of the rust client generator that are currently untested. This PR adds tests for various generator-specific types, and also files.
Follows the example of the rust-server generator for making it easy to add new test specs. This should make it easier for future contributors to make sure that their contributions are tested
