Casper Schmidt Wandahl-Liper
Casper Schmidt Wandahl-Liper
@fabiocav I can't get the work-around to run on Azure Functions V2: ``` [11-02-2020 12:50:13] A host error has occurred during startup operation 'e5061744-cc42-4f93-991a-71a3a52eb7e0'. [11-02-2020 12:50:13] Hemonto.Asset: Could not load...
@fabiocav no I mean V2 as in. Net core 2.2. My colleague tried migrating one of our services to V3 but it didn't work out-of-the-box and we're on a tight...
@fabiocav I have done some quick testing and I can confirm that on AZ V3 there are some issues binding querystring parameters to enum and lists (`IEnumerable`) (using a POST...
[FunctionAppHttpParameterTesting.zip](https://github.com/Azure/azure-webjobs-sdk-extensions/files/6264580/FunctionAppHttpParameterTesting.zip) Here's a small example. I have attached three requests in a Postman collection as well. Enabling and disabling the querystring parameters that maps to `enum` or `IEnumerable` will either...
@fabiocav any news here?
Still nothing? I'm amazed that a bug/severe limitation like this get so little attention :(
@rahul230691 the only workaround I know of is to do the deserialization yourself using Newtonsoft/Json.Net but this is not easy if you have values in both querystring and body.
@fabiocav @jeffhollan could you at least give some kind of response?
It appears to also be a problem for net6.0 on Functions V4 (referencing Microsoft.NET.Sdk.Functions 4.1.1) @fabiocav @jeffhollan
@v-anvari not exactly. I don't need both a POCO and HttpRequest object. What I'm looking for is the possibility of having the POCO being immutable (all properties being get-only) after...