Enhance OpenApi nesting with tags support #932
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commits enhances the
OpenApi
nesting support by adding possibility to definetags [...]
for the nested OpenApi endpoints. By default the fully qualified path to the nestedOpenApi
will become the tag for the endpoints if provided.This commit also makes it necessary to define the argument names within the nest tuple to be constant across the utoipa macros and more readable.
Path
andapi
arguments are necessary.Supported nesting syntax:
Breaking! This is breaking change as this changes the
utoipa::Path
trait syntax to following. Prior this commit thepath_item
function tookOption<&str>
parameter to define defaulttag
for the path operation but this is no longer necessary.Follow up PR for #930
Resolves #445 Resolves #872