-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
OpenAPI: Added AutoTag and Response for Auto Security Requirement #19464
Conversation
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building f16c03f
Full information is available in the Build summary check run. Test Failures⚙️ MicroProfile TCKs Tests #📦 tcks/microprofile-openapi✖
✖
|
Signed-off-by: Phillip Kruger <[email protected]>
It would probably be best to get a review from someone else (@michalszynkiewicz maybe?) because I won't be back for a few more days |
Thanks, apologies I did not know you are away. |
NP! |
@phillip-kruger Hi, I'm not very familiar with this code but the idea of the What does thanks |
@sberyozkin at the moment if an operation is not tagged, it's all grouped under "default" (see swagger ui screen). This will group them automatically by class (using the ClassName but making it readable, so Class Name). A user can still use the tag annotation, and in that case we will not auto tag. |
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.
LGTM
This PR adds a AutoTag filter that will tag an operation with the class name. (if it's not explicitly tagged in annotations)
It also refactors the Auto Roles Allowed filter into it's own filer (from the SecurityConfig Filter) so it can apply even if security in not added with config.
Signed-off-by:Phillip Kruger [email protected]