-
(I am using axum and the axum bindings)
I noticed that to completely export a type I also have to list all subtypes in the components.
While this offers 100% felxibility, I am trying to export gener…
-
Because it's easy to accidentally forget to include a schema for a new struct in the Utoipa macros, we should add linting for OpenAPI specifications in GitHub Actions.
_Originally posted by @praseo…
-
Dot-P updated
1 month ago
-
Hello 👋🏻
I'm trying to use this crate to automatically list my routes and models in the the utoipa macro. I tried to modularize my API into nested modules, each containing a `models` and a `routes`…
-
How would I use a struct from an external crate as a component. I want to use the `ValidationErrors` struct from the `validator` library.
-
see https://github.com/juhaku/utoipa/actions/runs/10779351123/job/29892650558?pr=1036 and other jobs
The following error is repeated many times
```
if [[ true == true ]]; then
cargo clippy -…
-
## Requested feature
Add support for `#[schema(skip)]`
## What this does
When this attribute is present, the target field or variant will not show up in the generated OpenAPI spec. This is li…
-
Recently I was evaluating using `poem-openapi` instead of `axum` with `utoipa`, but ultimately went with the latter because of utoipa's integration with serde.
Just as an example, I have a struct w…
-
### Description and goal
In the error derive, we compute the type of error's context ( ie list its properties and their type).
For now the code is pretty simple and do manually the cast between si…
sim51 updated
7 months ago
-
Hi! :wave:
I'm playing around with this crate and ran into an issue where schemas (and I'm guessing paths) aren't detected when behind a `cfg_attr` flag. E.g:
Works:
```rust
#[derive(ToSchema)]…