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
We are currently unable to extract the request body from "examples". When attempting to fill in the value, the error message The property `application~1x-www-form-urlencoded` must have either `example` or `examples`, but not both, as they are mutually exclusive is displayed due to the "example" parameter being added when the request already has "examples".
Steps to reproduce
To reproduce the issue, follow these steps:
Parse the my-oas.json file (see below) using the following code:
The parsing is completed without errors, however, the resulting node is missing the expected value and contains an unexpected valueJsonPointer.
Expected result
The request body value should first be filled from the "examples", followed by "example". If both of them are absent, the "example" from the "schema" can be used as a last resort.
The text was updated successfully, but these errors were encountered:
Description
We are currently unable to extract the request body from "examples". When attempting to fill in the value, the error message
The property `application~1x-www-form-urlencoded` must have either `example` or `examples`, but not both, as they are mutually exclusive
is displayed due to the "example" parameter being added when the request already has "examples".Steps to reproduce
To reproduce the issue, follow these steps:
my-oas.json
file (see below) using the following code:/paths/~1api~1users/post
tree node contain the appropriate values:my-oas.json
Actual result
The parsing is completed without errors, however, the resulting node is missing the expected
value
and contains an unexpectedvalueJsonPointer
.Expected result
The request body value should first be filled from the "examples", followed by "example". If both of them are absent, the "example" from the "schema" can be used as a last resort.
The text was updated successfully, but these errors were encountered: