Chris Martinez

Apologies for the delay. I've been a bit backed up by my day job and personal life of late. To be clear, I am the _someone_ to review and merge...

This _might_ be a gap in the implementation. I can tell by what you've shared that you are in the _Partial OData_ camp. You're not really using OData the protocol....

Hmm... This _might_ actually be a bug. The generated EDM is **only** created and used by API Explorer. It's actually ephemeral. The workaround _should_ be to use the same model...

Apologies for the pain. You've done the work. Moving this issue up to the top of my queue and items to get pushed through. I will try to get this...

I would be very surprised that anything about `AddApiExplorer` caused this behavior. It doesn't change any routing behavior whatsoever. It's purely discovery. I can't say I have much firsthand experience...

For a little clarity, does this problem exist for all gRPC endpoints? I still need to deep dive on this, but looking back at the history, the problem seems to...

You mentioned you're upgrading from .NET 6, but you didn't say which version of API Versioning you were using. Based on the behavior you are describing, I'm guessing you are...

Following up. Did the explanation clarify things and resolve the issue? Were you able to find a workaround or solution? I _believe_ this issue has landed on this _this is...

Something is amiss here. This is strange. There is no path where this can happen by default. I presume you are using version `6.4.x`. ### Minimal APIs Versions and policies...

Following up. Is this still an issue? Did you ever resolve it?