Jonas Lagoni

> Because many people don't want to use AsyncAPI to define applications but a menu of channels, messages, servers, etc. Systems like event gateways are not interested in operations at...

I love the move to a property, whether `address` is the right keyword, not so sure, but I don't have other alternatives at the moment. What exactly is the reason...

Okay I retract my suggestion, you are right. Especially if you want to define two channels operating over the same address, with slightly different behavior, you would need to add...

Is there any of you who wants to champion this? 🙂 Or can we consider this issue as needs champion? 🤔

I think this makes sense to include in 3.0.0. My only concern is that it becomes difficult for tooling to access the full URL. As you rarely need to access...

Is there any of you who wants to champion this? 🙂 Or can we consider this issue as needs champion? 🤔

I am just gonna spark the discussion with a suggestion to how we can solve this problem. I suggest we change the layout of channels to be an array rather...

> 1. If channels is an array, it would be easy to have inconsistencies. For instance, you can have the `example` channel defined many different times each of them with...

But with the proposed setup this would not be a valid file though 🤔 ?

Ahh! Yes! Then I agree with you 😄