Vladimír Gorej
Vladimír Gorej
@magicmatatjahu yep I do understand that, thus I would expect the renderer to treat the `$ref` field as normal field name without any significance. Even if it would be supported...
Just describing my understand of `Message Example Object`.`payload` field in more detail here. The specification for AsyncAPI 2.6 says:  `any` means that arbitrary data can be provided there and...
Right, so it's basically an arbitrary `data` (that's what `any` means for me) that needs to be validated later against `Message.payload`, but it's still just `data`. If the `Message.payload` is...
Still reproducible in latest studio version.
Same issue here: Now using node v20.3.0 (npm v9.6.7)
Here is an excerpt from OpenAPI 3.0.3:  @frankkilcommins I think @ahdbk is right. We either have to do this modification: ```yaml requestBody: content: multipart/form-data: schema: type: object properties: orderId:...
@greenteaisgreat would you mind issuing a fixing PR?
You're right. It's not in the repo, it is in another private one.
cc @frankkilcommins
Hi @mnosov622, From I can tell, the cards you referring to are not part of this repo. This repo contains some public parts of https://swagger.io/, but couldn't find the card...