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
It looks like when using nested structure with allOf the properties of the inner object are not rendered properly by Swagger UI. Eg: render one object that is defined with allOf inside other object that is also using allOf.
Since both Container and Inner objects makes use of allOf, the properties FieldA and FieldB wont be rendered in the Swagger UI.
However, the properties are present on the Schemas generated by open-api-spex, so it doesn't look like an issue on the library, it looks more like an issue in the renderer.
On the other hand, this is a known issue on the Swagger renderer swagger-api/swagger-editor#2765 (comment), and one possible workaround to it is moving the paths field above the components on the JSON generated.
So, if the path field were in the top on the generated JSON specs, the properties of Inner would be rendered properly:
It is possible to control de order of the fields in the JSON specs generated? Thank you
The text was updated successfully, but these errors were encountered:
It looks like when using nested structure with
allOf
the properties of the inner object are not rendered properly by Swagger UI. Eg: render one object that is defined withallOf
inside other object that is also usingallOf
.For example, with this schema structure:
Defining
Container
andInner
as:Since both
Container
andInner
objects makes use ofallOf
, the propertiesFieldA
andFieldB
wont be rendered in the Swagger UI.However, the properties are present on the Schemas generated by
open-api-spex
, so it doesn't look like an issue on the library, it looks more like an issue in the renderer.On the other hand, this is a known issue on the Swagger renderer swagger-api/swagger-editor#2765 (comment), and one possible workaround to it is moving the
paths
field above thecomponents
on the JSON generated.So, if the
path
field were in the top on the generated JSON specs, the properties ofInner
would be rendered properly:It is possible to control de order of the fields in the JSON specs generated? Thank you
The text was updated successfully, but these errors were encountered: