add support for non-wrapped collections responses

[baywet]

I've had a few more attempts in the last three weeks and still not working. I've had different errors over this period .. with today's being different again.

This is the latest error(s): (sorry the images are so wide)

Note that I've just pulled 1.0.4 for one of the packages.

dotnet.csproj

<Project Sdk="Microsoft.NET.Sdk">

  <ItemGroup>
      <PackageReference Include="Microsoft.Kiota.Authentication.Azure" Version="1.0.3" />
      <PackageReference Include="Microsoft.Kiota.Serialization.Json" Version="1.0.3" />
      <PackageReference Include="Microsoft.Kiota.Http.HttpClient" Version="1.0.4" />
  </ItemGroup>

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net5.0</TargetFramework>
  </PropertyGroup>

</Project>

and the client was generated with latest code from main branch, which I just pulled down about 15 mins ago.

Thoughts? I'm wondering if this is my fault, now?

Originally posted by @PureKrome in #135 (comment)

Note: this is due to the fact that Microsoft Graph always wraps collections in response objects, but not all APIs do that. The Http Core interface needs a new method returning enumerable of parsable (and maybe one for primitives too?). And the generation logic needs to be updated to switch the method based on the collection kind.
AB#10607

[baywet]

Hi @PureKrome
Thanks again for the super valuable feedback you are providing!
I put together PR #480 to fix this issue, which will close it when merged.
As always, you can resume your testing and work on #135 by using the branch of the pull request instead of main. Happy coding.

[baywet]

Note: the packages won't align with the generation result until published, you might want to use local references if testing from the PR.

[PureKrome]

Thanks heaps @baywet !!

Note: the packages won't align with the generation result until published

When are packages "released"?

[baywet]

you're welcome! just about now. :)

[PureKrome]

ha woot!