Vladimír Gorej

This issue is https://github.com/swagger-api/swagger-codegen related. Transferring the issue.

Yeah, let's do it!

Hi all, - added [research notes](https://github.com/asyncapi/spec/issues/1129#issuecomment-3643844649) to https://github.com/asyncapi/spec/issues/1129 from which the https://github.com/asyncapi/spec/pull/1135 was produced - added approval for https://github.com/asyncapi/spec/pull/1109 with an attached [comment](https://github.com/asyncapi/spec/pull/1109#issuecomment-3643911645) - made myself familiar with https://github.com/asyncapi/spec/issues/1143 -...

Closing this in favor of https://github.com/swagger-api/swagger-ui/pull/10192. The base image is already updated on `master` branch. Unfortunately we'll also not going to go for full `apk upgrade --no-cache` change. Adding apk...

@sahilpatil2997 https://hub.docker.com/layers/swaggerapi/swagger-ui/v5.18.1/images/sha256-ae37cdb99e6440c29c693a39770b6e87dffb6651c7766565f2922ef06b549e93?context=explore

Reopening this as it's confirmed now that this is unrelated to https://github.com/swagger-api/swagger-ui/issues/3832

The swagger-client either creates unnecessary nesting instead of stopping on first detected cycle. It might also be the case that the resolver is functioning OK, but then the SwaggerUI is...

Hi everybody, Some of my thoughts after research: We haven't had this problem in AsyncAPI 2.x. We had a [Security Requirement Object](https://v2.asyncapi.com/docs/reference/specification/v2.6.0#securityRequirementObject) which was creating implicit connection with Security Scheme...