Chris Martinez

This is a rare edge case, but it is the expected behavior. The `$metadata` endpoint, like the API Explorer, collates API versions from all OData controllers. If all of the...

There wasn't any additional follow-up or push-back. This behavior is expected and is an unfortunate limitation and edge case that is effectively nonsensical in a real application. I _could_ document...

This behavior is expected albeit not as obvious as one might expect. The discussion appears to have gone idle and I don't think there's any more to do. If there,...

I see what happened. I'll consider this a bug. Honestly, this _feels_ like a bug in `System.Net.Http`, but I doubt I'll move the mountain much if I file an issue....

First, a point of clarity. The issue indicates you are targeting .NET 7, but the text says ASP.NET Core 6, which would be .NET 6. .NET 8 is the current...

Thanks for the repro. It has been useful. It turns out that I had a repro, but I kept missing the scenario. This is a bug. The reason this happens...

You're _supposed_ to be able to. I've noticed another bug. 😞 I over-optimized the support for grouping and I now realize that if you **only** use a group name the...

People _still_ actually use collection parameters? 🤔 🤣 Sadly, this is _kind of_ a big deal. The solution is not so simple. This is more of an issue with OData...

Nice! Glad to see you moving to the new. The migration is a little rough, even with just plain 'ol OData, but the end result is largely better. ### Issue...

Whoops! It should be: ```c# options.ModelBuilder.ModelBuilderFactory = static () => new ODataConventionModelBuilder(); ``` I've updated the comment. That's what happens when you try to do it all from memory. 😄