You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using aide on an API with some String and Uuid path parameters and just figured out through trial-and-error that they need to be wrapped in a struct type to have openapi parameters correctly generated for them. Now that I've discovered it, this makes some amount of sense, but I'd love to have it documented explicitly somewhere (Apologies if it already is, I couldn't find it).
I haven't finished going through my API yet so I'm not sure if this true of query parameters as well.
What I did
This happily compiled, but generated me an openapi route with no parameters:
I've been using
aide
on an API with someString
andUuid
path parameters and just figured out through trial-and-error that they need to be wrapped in a struct type to have openapi parameters correctly generated for them. Now that I've discovered it, this makes some amount of sense, but I'd love to have it documented explicitly somewhere (Apologies if it already is, I couldn't find it).I haven't finished going through my API yet so I'm not sure if this true of query parameters as well.
What I did
This happily compiled, but generated me an openapi route with no parameters:
I had to switch to something like this to get documentation generated:
An easy repro
This is really easy to reproduce with the
example-axum
example. If you switch to a plainUuid
the path parameter disappears!The text was updated successfully, but these errors were encountered: