Null results not handled correctly in Java client

[BrennanConroy]

We don't differentiate between a null result and no result in the Java client today. Looking at the .NET client we have a hasResult parameter when constructing the CompletionMessage

aspnetcore/src/SignalR/common/SignalR.Common/src/Protocol/CompletionMessage.cs

Line 36 in e9a9108

public CompletionMessage(string invocationId, string? error, object? result, bool hasResult)

vs. no hasResult in the Java client.

aspnetcore/src/SignalR/clients/java/signalr/core/src/main/java/com/microsoft/signalr/CompletionMessage.java

Line 15 in e9a9108

public CompletionMessage(Map<String, String> headers, String invocationId, Object result, String error) {

This causes code like below to never complete the client-side invoke:

class MyHub : Hub
{
    Task<string?> Get()
    {
        return Task.FromResult<string?>(null);
    }
}

connection.invoke(String.class, "Get").blockingGet();

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.