You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start prism with the provided endpoint2. curl -X POST http://127.0.0.1:4010/pet3. Observe output
Expected
Should return 200 and a lorem ipsum response
Actual
Returns an error
{"type":"https://stoplight.io/prism/errors#UNPROCESSABLE_ENTITY","title":"Invalid request body payload","status":422,"detail":"Your request body is not valid: [{\"path\":[\"body\"],\"code\":\"type\",\"message\":\"should be object\",\"severity\":0}]"}
Context
We currently don't check the required field when validating body. The proposed solutions is that HttpBodyValidator should extend HttpParamsValidator class.
The text was updated successfully, but these errors were encountered:
Prerequisites
Steps to reproduce
curl -X POST http://127.0.0.1:4010/pet
3. Observe outputExpected
Should return 200 and a lorem ipsum response
Actual
Returns an error
{"type":"https://stoplight.io/prism/errors#UNPROCESSABLE_ENTITY","title":"Invalid request body payload","status":422,"detail":"Your request body is not valid: [{\"path\":[\"body\"],\"code\":\"type\",\"message\":\"should be object\",\"severity\":0}]"}
Context
We currently don't check the required field when validating body. The proposed solutions is that
HttpBodyValidator
should extendHttpParamsValidator
class.The text was updated successfully, but these errors were encountered: