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
We have 2 tabs in our Angular application- API references and Schema view. In the API references tab, we do not want to show the schema at the bottom, while in the Schema view tab, we want to show the schema only.
The visibility of schema depends on the order of clicking the tabs.
On navigating to API references tab first, the output is expected. Schema is not displayed below. However, if I click on the Schema view tab next, the schemas are not displayed, despite the different configurations as mentioned above.
On navigating to Schema view tab first, the schemas are displayed as expected. However, clicking on API references tab next, the schemas are displayed at the bottom.
On refreshing, everything disappears.
Expected behavior
API Reference tab should not render schemas.
Schema view tab should render only schemas.
Refreshing should not make everything disappear.
Additional context or thoughts
This issue exists only for OAS 3.1; Swagger 2.0 and OAS 3.0 render as expected. This implies that our application logic is not particularly at fault here.
The text was updated successfully, but these errors were encountered:
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Swagger-UI configuration options:
Describe the bug you're encountering
We have 2 tabs in our Angular application- API references and Schema view. In the API references tab, we do not want to show the schema at the bottom, while in the Schema view tab, we want to show the schema only.
The visibility of schema depends on the order of clicking the tabs.
On refreshing, everything disappears.
Expected behavior
Additional context or thoughts
This issue exists only for OAS 3.1; Swagger 2.0 and OAS 3.0 render as expected. This implies that our application logic is not particularly at fault here.
The text was updated successfully, but these errors were encountered: