-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix: added fix to validate for top-level type in parameter schemas while using oneOf in request-validator plugin. #215
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #215 +/- ##
==========================================
- Coverage 69.08% 68.97% -0.11%
==========================================
Files 24 24
Lines 3290 3343 +53
==========================================
+ Hits 2273 2306 +33
- Misses 848 864 +16
- Partials 169 173 +4 ☔ View full report in Codecov by Sentry. |
45ac9b7
to
a9aa487
Compare
openapi2kong/oas3_testfiles/17-request-validator-plugin-oneOf-usage.expected.json
Show resolved
Hide resolved
schemas while using oneOf in request-validator plugin. As of now, deck file openapi2kong command was not checking for multiple types used while creating parameter schemas with oneOf, which is not supported by Kong request- validator plugin. Thus, we are forcing for defining a top-level type property and erroring out in case it is not present.
bd052a6
to
10162c3
Compare
the uncertainty in maps iteration order in golang
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.
since we're at a tie, let's get this done 😄
As of now, deck file openapi2kong command was not
checking for multiple types used while creating parameter schemas with oneOf, which is not supported by Kong request- validator plugin. Thus, we are forcing for defining a top-level type property and erroring out in case it is not present.
Fixes: #206