Fran Méndez

> as SSE has its own logical channel of application defined messages 🤔 This wasn't obvious to me at first glance. Can't we map AsyncAPI channels to these logical channel...

Then I think http://example.com should be a server definition and `/server/sent/events` should be the address of the channel. So better to keep it out of the sse binding. What do...

Yeah, exactly. That would simplify things IMHO. The server protocol could be `http` or `http+sse`. Either way should be fine.

Yeah now there's nothing in the AsyncAPI document saying that this API MUST use SSE. It only defines that "when using SSE", this message's event type is X. IMHO, there...

I'm labeling as `good first issue` not because it's an easy-to-solve bug in terms of coding experience but because it's a good way to get familiar with how automation works...

I honestly have no idea about the underlying issue. Just came here to say that [OpenTofu](https://opentofu.org/) is now the OSS version of Terraform and we might have to switch to...

I'm all in with this proposal. Just want to leave a note on the following: > This inherently implies that all messages are of the same version, or that events...

> Do you want to edit my message/proposal ? No, I think that's fine. Just wanted to clarify it 👍

FYI, I've created the account already. It's `[email protected]`. It's using the `.com` instead of the `.io` because we're migrating all mailboxes there as the `.io` is not owned by Linux...

This requires a PR in the github.com/asyncapi/parser-js too, so we can pass this info to the resolvers. It may even requires us to build a custom HTTP resolver.