-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Added noRequestBody function to check that HTTP GET and DELETE methods do not contain a requestBody #588
base: main
Are you sure you want to change the base?
Conversation
…s do not contain a request body
…ave a requestBody
…o-request-body-oas-func # Conflicts: # functions/functions_test.go
Formats: model.OAS3AllFormat, | ||
Description: "HTTP GET and DELETE should not accept request bodies", | ||
Given: "$", | ||
Resolved: false, |
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.
@daveshanley I don't know what Resolved means. Should it be true or false here?
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.
Resolved means that the $ref
values have all been stitched together by the resolver
in libopenapi
This is used for rules that assume everything is resolved and inlined. It only makes a difference if the logic in your rule / function is recursive - if so, it means that any circular references could create an infinite loop.
@daveshanley bump :) |
Will get to this ASAP, apologies for my slowness. |
Requested from here: #582