Fran Méndez
Fran Méndez
CloudEvents compliant. The idea is to allow users of CloudEvents reuse their existing messages.
I'm gonna work on this for v3.0.0, that's all I can say so far. No plans to have it for v2.x.
> that's all I can say so far Just for the record, I meant "I haven't really looked at it in detail yet so don't know". Hope it didn't look...
That's a great suggestion, @jonaslagoni. I foresee a couple of issues at a glance: 1. If channels is an array, it would be easy to have inconsistencies. For instance, you...
Yes but nothing prevents you for doing something like: ```yaml example: example/: # channel, and keep the current object. parameters: # Channel parameters message: # Message for the channel regardless...
Sure. Just arguing that it's leaving a lot of room for failure. We should aim to make it less error prone.
I'd say so, yes.
Love how much effort you've put into this proposal 👏 ❤️ I have a few comments/questions: 1. I don't really get what's an endpoint. Is it a node in the...
We're already doing that at Schema Object level (same as in OpenAPI). The Schema Object is a pure JSON Schema object, not something OpenAPI or AsyncAPI defines.
I have a few concerns with this PR: 1. This PR is doing too much. Please let's keep PRs focused on one thing at a time. Server and Channel traits...