Mehmet Akbulut

Hi @webcoyote ! Thank you so much for this MR. Have you had a chance to test this change? I believe this should work without any side effects. I haven't...

Hi Danzel! I have been working on getting the source generator contributed to ASP.NET Core so hopefully these capabilities will be available out-of-box at some point. If you have the...

If you are already happy with source-generator over dynamic, I'd recommend staying with the source-generator though.

I see this same issue with `403` on version `1.5.2`. What should happen is: 1. BloomRPC makes a call 2. Server responds with 403 3. BloomRPC shows the call failed...

I'm all for having native support for conic sections (not sure what this "support" should look like) but, as an aerospace engineer by training, I don't think orbital propagation is...

> Alternative attribute names: `ServerHubProxyAttribute` - ServerHub sounds better than HubServer `ClientHubAttribute` - This represents a "client hub" not a proxy so this seems like a better name. @BrennanConroy I...

> My main issue with this approach is that you are forced to define all methods on the client side. That makes sense. I'm OK with restricting registration to a...

I'd suggest the following basic API surface. ```csharp // Get strongly typed hub proxy public T GetProxy(this HubConnection conn); // Register callback method and get a disposable which can unregister...

@nenoNaninu It appears what you are proposing is one layer higher than what I've proposed here. Your proposal essentially wraps proxy acquisition and callback registration behind a single base client...

Here is a more concrete proxy example. Given following interface in a shared/common project/library: ```csharp public interface IMyHub { Task DoSomething(); Task DoSomethingElse(float arg); IAsyncEnumerable StreamBidirectional(IAsyncEnumerable clientToServer, [EnumeratorCancellation] CancellationToken token);...