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
$ref objects that are marked as readOnly, and are not relevant for requests, still show up in the documentation and cause confusion.
Current Behavior
For any property marked as readOnly, that also uses a $ref, the read-only marking is not reflected in the documentation.
The readOnly is ignored, and the element shows up in requestBody elements, as well as in examples. In the schema section, the element is rendered without a "read-only" label.
Expected Behavior
The property set to readOnly should be omitted from request bodies, examples and be marked in the schema as "read-only"
$ref objects that are marked as readOnly, and are not relevant for requests, still show up in the documentation and cause confusion.
Current Behavior
For any property marked as readOnly, that also uses a $ref, the read-only marking is not reflected in the documentation.
The readOnly is ignored, and the element shows up in requestBody elements, as well as in examples. In the schema section, the element is rendered without a "read-only" label.
Expected Behavior
The property set to readOnly should be omitted from request bodies, examples and be marked in the schema as "read-only"
Steps to Reproduce
Given the following spec:
The patch endpoint gets rendered with an empty
video
element:... and looking at the schemas section for the Outcome, the read-only label is also missing from the
video
element:Note that the inlined
subtitle
object works as expected.Environment
The text was updated successfully, but these errors were encountered: