Fran Méndez
Fran Méndez
### Problem Currently, AsyncAPI servers have a property called `url`. In many cases, we're showing examples of the `url` field as a host instead (without the protocol part of the...
> **Note**: I'm gonna call it "AsyncAPI Domain spec" for the lack of a better alternative. Let me know if you have a better one 🙏 ## TL;DR 1. `channels`...
As of version 2.x, an AsyncAPI file represents an application. However, as we work on #618, other proposals have arisen to: 1. Make the AsyncAPI file also become a collection...
--- title: "Move operations to its own root object" --- --- **Related issue(s):** #618 #663 ---
## TL;DR: What's new? * **Remote vs Local Servers**: Servers got a new `kind` property. By default, all servers are `remote` servers (e.g., brokers). However, if the `kind` property is...
### Description I'm creating this issue to hold discussions about the problem with the publish/subscribe perspective. As it is right now, the perspective is from the "client". Let's put it...
[defaultContentType](https://github.com/asyncapi/asyncapi/blob/master/versions/2.0.0/asyncapi.md#default-content-type) doesn't have a default value and it's not listed on the AsyncAPI Object, even though it's at root level and must be there. Should we make this field mandatory...
It's currently very hard to reuse channel definitions across multiple AsyncAPI files. The reason is that they contain the operation definition too. An example: ```yaml channels: example: subscribe: message: payload:...
It would be great to have a way to flag that a channel is deprecated or is going to disappear/sunset at some point. We already thought about a property like...
https://github.com/stoplightio/spectral/pull/974#discussion_r408263640 Thanks, @nulltoken!