Maarten
Maarten
This is still needed 👍
I am also running into this issue. As I am generating a client, the deserialization will fail.
> I didn't have this problem until after I upgraded to Windows 11 and upgraded NVM. It worked fine before upgrading to 1.1.9 but downgrading now doesn't help. > >...
@Yao725 we have replaced the `ArmClient` call by a call to the `ARM Rest Api`, like so: ``` cs HttpResponseMessage response = await _httpClient.GetAsync($"https://management.azure.com/{resourceId}?api-version=2021-04-01"); response.EnsureSuccessStatusCode(); ``` This call isn't case...
How can I find out: - When will the SDK be released? - Which version should fix the issue?
I'm also curious if there's any update. This is a big issue when logging from an orchestration, options currently are: - Logging everything multiple times from orchestration, for each replay...
Why don't you pull the packages with this issue? For us this broke our Blazor website 😢 @MarvinKlein1508 thanks, I've added this workaround as a temporary solution!
Please fix this issue
Huge issue for us too. Tried kiota 1.29.0 and OpenApi versions 3.0, 3.1, kiota cannot make sense of nullable properties. [edit] OpenApi 2.0 seems to have issues generating nullable types,...