Vladimír Gorej

> Hi @char0n, it works, BIG THANKS. We are able to introduce asyncapi specs in addition to the openapi ones for our microservices architecture. Cool, be aware that the JavaScript...

Hi @mathematikoi, This looks legit. > the reference resolving correctly within the example schema as it has an id and should be treated as a resource schema. Expected behavior actually...

@clemensv thanks for the report. We assume that the `retrievalURI` is the current `window.location.href` because of the nature of the online editor living inside the browser. But I can see...

> For now we, we'll stick with last working version of @asyncapi/[email protected] with @asyncapi/[email protected]. This has been addressed in https://github.com/swagger-api/swagger-editor/pull/4586

All issues have been addressed in https://github.com/swagger-api/swagger-editor/pull/4446 ### Issue 1 `swagger-editor-cra` has been compensated to support Spectral and SwaggerEditor@5 provides instructions for webpack how to overcome Spectral bundling issues. ###...

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)...

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

This hasn't been addressed yet

Hi @philsturgeon, I'm sorry but I cannot reproduce. Used anonymous Google Chrome window and pasted your definition in. This is the result: 

> @char0n is it react component related? I would say yes. After further detailed investigation I can confirm that isomorpism of stringification works well, here is a proof: ```js import...