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
First of all, congratulations on building such an excellent tool! 👏👏👏
We have some models that are only be meant to appear in responses, never in requests. These components are marked as readOnly in their schemas, such as:
The problem is that, if we use Holder in the requestBody, the property "ro" appears in the visualisation of the request body schema. This is similar to #569, but not exactly the same.
In Swagger-UI the schema is rendered as expected; the "ro" field is hidden in the POST operation but visible in the GET.
Hi!
First of all, congratulations on building such an excellent tool! 👏👏👏
We have some models that are only be meant to appear in responses, never in requests. These components are marked as readOnly in their schemas, such as:
The problem is that, if we use Holder in the requestBody, the property "ro" appears in the visualisation of the request body schema. This is similar to #569, but not exactly the same.
In Swagger-UI the schema is rendered as expected; the "ro" field is hidden in the POST operation but visible in the GET.
Swagger-UI example
RapiDoc example
Using RapiDoc 9.1.3
The text was updated successfully, but these errors were encountered: