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
Hi, I have an issue when using oneOf in the schema. If the schema referenced by oneOf is a primitive type (like integer or string), only the type is shown in the documentation, not the details of the schema. But, if the schema is an object, the details are shown.
Expected behavior
Schema details should be shown for primitive types (example with redocly):
Current behavior
Only the type is shown for primitive types:
Full schema is shown for object type:
Steps to reproduce
Use the following openapi spec.
run yarn docusaurus gen-api-docs all && yarn start
Open docusaurus an go to the page that shows the API schema
In the example below, the Foo schema is an oneOf of 3 base schemas: two primitive types and one object.
I put the Foo schema in in the request body and the response, the result is the same: the object schema is shown as expected, but the integer and string schema are not.
Describe the bug
Hi, I have an issue when using
oneOf
in the schema. If the schema referenced byoneOf
is a primitive type (likeinteger
orstring
), only the type is shown in the documentation, not the details of the schema. But, if the schema is anobject
, the details are shown.Expected behavior
Schema details should be shown for primitive types (example with redocly):
Current behavior
Only the type is shown for primitive types:
Full schema is shown for object type:
Steps to reproduce
yarn docusaurus gen-api-docs all && yarn start
In the example below, the
Foo
schema is anoneOf
of 3 base schemas: two primitive types and one object.I put the
Foo
schema in in the request body and the response, the result is the same: theobject
schema is shown as expected, but theinteger
andstring
schema are not.Openapi spec
Context
Latest version of Docusaurus and OpenAPI plugin, fresh install.
The text was updated successfully, but these errors were encountered: