-
Notifications
You must be signed in to change notification settings - Fork 64
Add support for declaring path parameters on path item object instead of operation object #173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
12ff812
to
033703d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking that, a few comments.
Let's keep in mind that OpenApiLinks are currently generated based on the operation parameters: We still need to be able to generate these links even when the parameters are not available at the operation level. |
src/Microsoft.OpenApi.OData.Reader/Generator/OpenApiParameterGenerator.cs
Show resolved
Hide resolved
Thanks @irvinesunday for catching this (and the suggestion on how to handle it). I have pushed a fix for to resolve it c136516 |
@baywet @irvinesunday @xuzhg @darrelmiller kindly have a look at the PR. |
Co-authored-by: Vincent Biret <[email protected]>
c136516
to
b171a2d
Compare
Fixes #159
This PR add support for declaring path parameters on the path item object instead of the operation object. This feature is controlled by a new flag (
DeclarePathParametersOnPathItem
) onOpenApiConvertSettings
Example usage:
Example output