Passing query string parameters on method invocation about dotnet-sdk HOT 3 OPEN

@WhitWaldo As far as I know, query parameters were intended to "just work" with Dapr service invocation and simply "forwarded" to the application. You might submit an issue in the docs repo to have that be made explicit.

As far as a PR goes to help with query parameters, I'm a bit torn. On the one hand, it could be useful in that I've always thought .NET had unexpectedly poor support for managing query parameters. On the other hand, I don't necessarily want to create APIs that might be inconsistent with how developers typically manage query parameters in .NET.

I could see explicit support for query parameters in, say, the basic service invocation methods (e.g. in InvokeMethodAsync() pass a dictionary that represents the query). However, I'm not sure I can see explicit support for query parameters when working with HttpClient, as that seems more the purview of .NET itself or, at least, of non-Dapr libraries.

from dotnet-sdk.

@philliphoff Yes, my proposal was more centered on augmenting the InvokeMethodAsync method to include a query string argument as under the hood it's simply building out the URL to invoke the method out of the pieces provided, so we could simply add the query string to the end. It would make more sense to simply augment this method than necessarily add some extension method for the HttpClient returned from DaprClient.CreateInvokeHttpClient() as you're right, that's more the purview of the .NET team.

from dotnet-sdk.

/assign

from dotnet-sdk.