-
Notifications
You must be signed in to change notification settings - Fork 600
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
Correct handling of new properties added for OpenAPI 3.1 #30513
base: integration
Are you sure you want to change the base?
Correct handling of new properties added for OpenAPI 3.1 #30513
Conversation
fa6e772
to
f005aa3
Compare
...pi.2.0.internal/src/io/openliberty/microprofile/openapi20/internal/ApplicationProcessor.java
Show resolved
Hide resolved
Warn if the user has used annotation parameters which correspond to features added in OpenAPI 3.1 but they have configured use of OpenAPI 3.0.
f005aa3
to
bb99aca
Compare
#build (view Open Liberty Personal Build - ❌ completed with errors/failures.) Note: Target locations of links might be accessible only to IBM employees. |
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
bb99aca
to
e563498
Compare
- SmallRye OpenAPI 4.0.6 - Jandex 3.2.3 (prereq of OpenAPI) This includes a fix to not output properties introduced in OpenAPI 3.1 when generating an OpenAPI 3.0 document.
e563498
to
4bb5691
Compare
#build Note: Target locations of links might be accessible only to IBM employees. |
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
@@ -0,0 +1,144 @@ | |||
/******************************************************************************* | |||
* Copyright (c) 2024, 2025 IBM Corporation and others. |
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.
Given this is a new file should it have 2024?
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.
It would, but it's not new, it was extracted from OpenAPIVersionConfigImpl
.
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.
It used to be internal to that class, but I needed to use it in the new OpenAPIVersionUsageChecker
so I moved it into its own class.
Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_Mo04IM9KEe-f-sI4gb7_Pw Target locations of links might be accessible only to IBM employees. |
Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_zZ-2YM_TEe-f-sI4gb7_Pw Target locations of links might be accessible only to IBM employees. |
release bug
label if applicable: https://github.com/OpenLiberty/open-liberty/wiki/Open-Liberty-Conventions).Properties added in OpenAPI 3.1 are no longer processed when reading and writing OpenAPI 3.0 documents
Previously, the property would sometimes be output anyway, creating an invalid OpenAPI 3.0 document.
A warning is emitted if an OpenAPI annotation property from OpenAPI 3.1 is used but the user has requested OpenAPI 3.0 output in their configuration
We want a warning to tell the user that their annotation will be ignored because of the OpenAPI version they've configured.
Fixes #30036
Fixes #30514