Add security details to generated OpenAPI specs#74
Merged
Conversation
…will be included in the OpenAPI document generated
euano
commented
Mar 2, 2026
src/main/java/org/alfasoftware/soapstone/SoapstoneOpenApiReader.java
Outdated
Show resolved
Hide resolved
lucyr82
requested changes
Mar 3, 2026
Contributor
lucyr82
left a comment
lucyr82
left a comment
There was a problem hiding this comment.
Looks good but I think we should leave the security fields off entirely if nothing is passed through. It will minimise changes for existing usages. I've also found some evidence that an empty security schemes object may not be valid.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.