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
When displaying a request body schema, there is no indication of which properties are required and which are optional. Thee is no indication, regardless of whether table or object view is used.
In the above example, the email_address property is marked with required: false in the OpenAPI spec, whereas the other two properties are marked as required: true, but there is nothing to indicate this in RapiDoc.
The text was updated successfully, but these errors were encountered:
can you provide me with a sample spec to reproduce the issue ?
testing with v9.3.6 Refer to this test case which annotates all the required and deprecated fields as expected
When displaying a request body schema, there is no indication of which properties are required and which are optional. Thee is no indication, regardless of whether table or object view is used.
In the above example, the
email_address
property is marked withrequired: false
in the OpenAPI spec, whereas the other two properties are marked asrequired: true
, but there is nothing to indicate this in RapiDoc.The text was updated successfully, but these errors were encountered: