Skip to content

[ENG-987] Handle non-existent security requirement in “konfig fix”#79

Open
dphuang2 wants to merge 1 commit intomainfrom
ENG-987
Open

[ENG-987] Handle non-existent security requirement in “konfig fix”#79
dphuang2 wants to merge 1 commit intomainfrom
ENG-987

Conversation

@dphuang2
Copy link
Contributor

@dphuang2 dphuang2 commented Jul 24, 2023

basically, if an operation is referring to a non-existent security requirement we should just auto map it to an existing security requirement with the lowest edit distance as the non-existent security requirement was most likely a typo

we should make this a lint rule too

@notion-workspace
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant