Open frankkilcommins opened 10 months ago
For OpenAPI 2.0 and 3.0.x this should be a configuration change.
For OpenAPI 3.1.0 we need to check if the new JSON Schema 2020-12 renderer (used with OpenAPI 3.1.0 definitions) supports rendering the extensions at all.
@char0n additional work will have to be done to accommodate the new renderers. Suggest to split that out into a separate issue.
Extension rendering enhancement for OpenAPI 2.0/3.0.x is being handled in: https://github.com/swagger-api/swagger-ui/issues/9377
Extension rendering for OpenAPI 3.1.0 is being handled in: https://github.com/swagger-api/swagger-ui/issues/9376
:tada: This issue has been resolved in version 5.0.0-alpha.81 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This hasn't been addressed yet
@char0n @frankkilcommins we (SAP) made this contribution to AsyncAPI UI component: https://github.com/asyncapi/asyncapi-react/pull/994
Hi @pavelkornev,
- We need a way to pass the configuration to AsyncAPI plugin via Swagger UI constructor. Is there a way already?
Extracted in https://github.com/swagger-api/swagger-editor/issues/5006 and resolved there.
- We need a similar extension mechanism for OpenAPI rendering. Are you open for a similar contribution to Swagger UI component as we did to AsyncAPI UI? If so, we will prepare a PR.
This is a multi-step effort, we'll be addressing this in foreseeable future.
SwaggerEditor@Next does not enable the
showExtensions
property when initializing SwaggerUI.This is a regression in SwaggerEditor@Next for OpenAPI. The heritage version of SwaggerEditor supports it as well as AsyncAPI extensions being supported in the Next version of the editor.
SwaggerEditor@Next:![new_ui](https://github.com/swagger-api/swagger-editor/assets/15875424/b4d90500-8aa3-4f24-9ba2-54851637e814)
SwaggerEditor:![old_ui](https://github.com/swagger-api/swagger-editor/assets/15875424/fc29e96a-9db3-4811-a068-5bee0343c735)