Timon Back

Thank you @dabeck81 for this great contribution and following through the feature in multiple steps!

Hi @cer, Thank you for the report and versioned gists. In the latest revision (2), springwolf-ui renders the messages and operations, only the binding is missing. You probably want to...

Hi @cer, Great to see you building your custom plugins! We started looking into how to validate the provided AsyncAPI files in springwolf-ui (https://github.com/springwolf/springwolf-core/pull/1219), so that better error messages are...

Hi @cer, I plan to read the AsyncAPI spec in more detail on Friday, but want to give you a quick response now. Springwolf currently covers request/reply semantics for fixed...

Hi @cer, we included a small improvement https://github.com/springwolf/springwolf-core/issues/1216 in todays release: 1.12.0. > springwolf-ui is unable to render AsyncAPI compliant documents, which use a runtime expression in channel.location within reply...

What are the next steps? (Do I need to ping someone/post somewhere for a review) The channel binding contains the two new fields ˋnameˋ and ˋchannelˋ, which @Pakisan mentions in...

@Pakisan Is there something I can do to support?

Great. I just rebased the branch, tests are still green - however amqp 0.4.0 is not under test. I assume that is what you `will patch` @Pakisan? Yes, the implementation...

Thanks for the help, adding tests for the bindings has paid off. @Pakisan I updated the PR. Does the `schemas/3.0.0.json` file need to be updated as well (via bundler)? I...

@jonaslagoni My understanding based on @Pakisan comment is, that this is the correct change. Comment: https://github.com/asyncapi/bindings/pull/259#issuecomment-2314601080 The other PR is obsolete, I am happy to close it.