Luke Frisken
Luke Frisken
Perhaps wrap strings with braces: `{mystring}` or something similar.
Perhaps some of the `rust-embed` debug options to access the files via the file system can help with this?
Representations of types/paths which are parsed into schemas are spread throughout `utoipa-gen` and their level of parsing support varies: + https://github.com/juhaku/utoipa/blob/6cec1029f57e3fd81d6b2c7e4680c34e482060e6/utoipa-gen/src/ext.rs#L21 + https://github.com/juhaku/utoipa/blob/6cec1029f57e3fd81d6b2c7e4680c34e482060e6/utoipa-gen/src/ext/rocket.rs#L118 + https://github.com/juhaku/utoipa/blob/6cec1029f57e3fd81d6b2c7e4680c34e482060e6/utoipa-gen/src/ext/rocket.rs#L75 + https://github.com/juhaku/utoipa/blob/6cec1029f57e3fd81d6b2c7e4680c34e482060e6/utoipa-gen/src/lib.rs#L806 which is used...
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`
```rust #[derive(Component)] struct Foo { field: Option } ``` produces: ```json { "properties": { "field": { "$ref": "#/components/schemas/Self" } }, "type": "object" } ``` expected: ```json { "properties": { "field":...