-
Couldn't load subscription status.
- Fork 0
fix: collect only security and security schema changes relevant for the operation #45
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
base: feature/performance-optimization
Are you sure you want to change the base?
fix: collect only security and security schema changes relevant for the operation #45
Conversation
…ration when creating single operation specification
…ecurity-changes-classification
…are no components
|
|
||
| return { | ||
| asymmetricMatch: (actual: SecuritySchemesObject): boolean => { | ||
| if (!actual || typeof actual !== 'object') { |
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.
how is this possible if actual receives only objective type?
| version: 1.0.0 | ||
| security: | ||
| - OAuth2: | ||
| - read |
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.
changed both schema key and array. is it correct?
| title: Security Test | ||
| version: 1.0.0 | ||
| security: | ||
| - ApiKeyAuth: [] |
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.
empty array here is a little bit confusing. can't we get rid of it if it has no effect on the case?
fix: collect only security and security schema changes relevant for the operation
fix: only include root security and security schemes relevant for operation when creating single operation specification