utoipa
utoipa copied to clipboard
juhaku
Simple, Fast, Code first and Compile time generated OpenAPI documentation for Rust
At the moment if a field is marked with `#[serde(default)]` it is still noted as a required field in the generated openapi schema.
It looks like setting the response body to `Any` doesn't work as expected, it tries to reference it as a component. ```rust responses( (status = 200, body = Any) )...
It would be nice to check json examples by optionally attempting to serialize them for types that implement `Serialize`, this way examples are ensured to be valid. Perhaps a new...
It would be nice to have a way to override a field property derive with a manual implementation in a similar style to serde serialize_with. Perhaps the comment for the...
I can't figure out is it possible with the path macro to specify a response that returns a binary file for the body, say with `Content-Type` as `application/octet`
Hope support, Thank you very much!
```rust #[derive(Component)] struct Foo { field: Option } ``` produces: ```json { "properties": { "field": { "$ref": "#/components/schemas/Self" } }, "type": "object" } ``` expected: ```json { "properties": { "field":...
Route tags/namespaces at the moment are generated by what is provided in `handlers`. Might there be a way to specify renames for these tags so that they can be more...
```rust #[derive(Component)] struct Bar { foo: (String, String) } ``` or ```rust #[derive(Component)] struct Bar { foo: (String) } ``` I get the following error message: ```text unexpected type in...
Running `cargo check --all-features` on master currently produces the following errors: ``` error[E0119]: conflicting implementations of trait `ext::ArgumentResolver` for type `ext::PathOperations` --> utoipa-gen/src/ext/rocket.rs:23:1 | 23 | impl ArgumentResolver for PathOperations...