Alex Wichmann

> @VisualBean @yurvon-screamo are either of you familiar with aspnetcore? I haven't kept up to date with the recent changes to endpoints vs middleware. Middleware structure looks fine. My only...

> @VisualBean / @yurvon-screamo is this anything that you recon will be added to core? I have a use case in which I want to have our asyncapi files generated...

## JSON Schema files for AsyncAPI Single source of truth for the AsyncAPI specification. Used by parsers and other tools to validate whether they got it right or not. TCK...

This should be easy enough once asyncapi.net has replaced the models. I am technically working on this, although currently on parental leave so i don't have time until May to...

I'm currently working on implementing avro for message schemas,and then picking up 3.0 right after that. So hopefully won't take too long now.

If you make a branch and start migrating to asyncapi.net, the 3.0 will of course have breaking changes, but all of the reading and writing will mostly stay exactly the...

Not completely sure what you mean; but essentially you would need a map (if you can't infer it some other way) if you point me at some code I might...

Asyncapi.net uses system.text.json, so this will also be solved by the migration to asyncapi.net

Once moved to asyncapi.net this will be easy enough. It has full support for 'custom' bindings, and will provide a centralised place to add more as needed.

> @m-wild @VisualBean @yurvon-screamo > > Any chance of closing this PR? First off, it doesn't compile. Also looking at the commentary from the PR that introduced the change in...