Chris Martinez

Interesting trick. Sadly, this is a bug. Unfortunately, the OData routing quite difficult to work with under the hood. I've had to fork a big chunk of it. Although `7.x`...

`6.0` with support for OData `8.x` is now available. Is this issue still relevant? This definitely is a bug, but if there is no interest in continuing to work on...

@GitHub-TC There's a very real chance this was a bug and not functioning as expected. For `5.x` with OData `7.x` we may never know. Until MS unblocks my ability to...

This issue has a working solution and several alternatives. `5.1` has been published standalone and the `6.1.` packages have been published, which will definitely resolve this issue the _correct_ way....

I'm going to call this a 🐞 simply because it didn't do what you expected. There is a significant refactor in _Preview 3_ that will address this. Effectively, the API...

😲 Do you have a repro or more details you can share? Are you saying there is some previous version of API Versioning where this didn't happen? The response type...

Thanks for the repro. This will give me something to look at and compare against. Honestly, I can't think of a place where the response types would be changed or...

Ok. I found the problem. It's not that the response is changed per se, but descriptors are _cloned_ for each API version so that they don't result in side effects...

The closed issue dotnet/aspnetcore#9324 seems to confirm that these are the default, expected media types. 😢

`6.0` has been officially released and contains the fix on the API Versioning side. I'll do what I can to join the discussion on the ASP.NET Core side. Thanks for...