Michael Wildman

In theory you can use the `IAsyncApiDocumentProvider.GetDocument()` to retrieve the document without needing the http pipeline or middleware. I guess the question is when/where would you do this... Perhaps as...

In theory this is supported. Currently you'd have a couple of options for generating the AsyncAPI components: 1. Use the saunter-provided attributes. These should be added to your MQTT controller...

Thanks, I will take a look over the next few days.

Ok, there are a couple of issues with Option 2... 1. Saunter `DocumentFilterContext` does not expose the `ISchemaGenerator` -- easy fix from my side. 2. MQTTnet.AspNetCore.AttributeRouting does not provide any...

@alan994 sorry have been on Xmas holidays. I Will get to this in the coming week 🙂

@RicoSuter would you like me to complete the work on this one?

This is partially supported by the `` XML tag. It will use that as an example in the property definition. ```csharp /// /// Bar /// public string Foo { get;...

Hi, I don't have any experience using SignalR personally. But it's definitely something that I want Saunter to support. If you are happy to work on it I would accept...

I think you'd have to implement a new `IDocumentGenerator`. The current implementation is focused on scanning assemblies to find classes & methods with the Saunter-specific attributes, I don't think it...

Hi @Serg046, that's for offering to help. I think we would just need a class like the example filter above. As for bindings, SignalR should probably use websockets bindings https://github.com/asyncapi/bindings/blob/master/websockets/README.md...