Make value field in SecurityRequirement pub#1494
Open
marlonbaeten wants to merge 1 commit into
Open
Conversation
CommanderStorm
suggested changes
May 5, 2026
CommanderStorm
left a comment
CommanderStorm
left a comment
There was a problem hiding this comment.
- Can you change this to
impl Iteratorinstead or would this not solve the issue at hand for you? - Can you add a quick test so that if there are regressions, a test catches this?
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.
In our project we use the
OpenApidata structure to test our implementation corresponds to our documentation. However we cannot acces the the value ofSecurityRequirementwithout serializing the struct.We propose to make the value field
pub.