Use sets for OpenAPI security settings #687
Merged
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.
This commit updates the OpenAPI document and Operation object builders
to use sets for storing their security settings instead of lists. Each
entry in these collections can be safely made unique, as duplicates would
represent an "A or A" posture. Having multiple entries can cause issues
with consuming the output document.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.