-
Notifications
You must be signed in to change notification settings - Fork 92
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
Endpoints with OPTION method not added to generated OpenAPI spec #1246
Comments
altro3
added a commit
to altro3/micronaut-openapi
that referenced
this issue
Oct 11, 2023
No, it's just a bug. Fixed here: #1248 |
Thank you for the quick response. |
graemerocher
pushed a commit
that referenced
this issue
Oct 12, 2023
Hi @altro3, when are you planning to release this fix ? |
@jayeshkapadnis hi! Hm... I don't know when next released planned, but I thought that we can wait micronaut core 4.2.0 release and also fix KSP support. Also I want to release these new features - #1254 and #1233 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
I am trying to upgrade my application from Micronaut version 3.8.7 to 4.1.3.
We use
micronaut-openapi
to generate specs yaml. We have few apis with Http MethodOPTION
to ensure we can add an extension details to it.With changes as part of PR #1067, when
SchemaUtils.setOperationOnPathItem
is invoked it doesn't consider any HttpMethods fromHEAD
,OPTIONS
&TRACE
. Earlier it was part ofAbstractOpenApiEndpointVisitor.setOperationOnPathItem
.Is there a specific reason to remove these ? Is there any workaround to include endpoints with these methods in generated OpenAPI spec ?
The text was updated successfully, but these errors were encountered: