Chris Martinez

This will be reverted in _Preview 3_, which would alleviate this problem. It should be published - _soon_. 😉 I'll leave this unresolved until you can confirm you're getting the...

🤣 HA! No, not quite. After a long discussion and some refactoring, the mechanisms by which you provide intrinsic metadata will be reverted back to how they were/are. You can...

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

`6.0` is officially released and has the same setup as in _Preview 3_. This should feel _natural_ and coherent with how the metadata is applied, even without API Versioning. In...

I can't think of anything in API Versioning that would care about this. There are only a handful of places where the _special_ built-in OData types such as **ODataQueryOptions** matter....

I believe that you have something working. However, there is no such [official] interface as **IODataQueryOptions** as can be seen [here](https://github.com/OData/WebApi/blob/master/src/Microsoft.AspNet.OData.Shared/Query/ODataQueryOptions.cs) and [here](https://github.com/OData/WebApi/blob/master/src/Microsoft.AspNetCore.OData/Query/ODataQueryOptions.cs). You also shouldn't need `[FromQuery]` because your...

Do you have, or can you provide, a version of your code that demonstrates the problem and can be uploaded to this issue for further investigation?

I realize it's been quite some time. Thanks for the repo. I haven't run it - yet. API Versioning doesn't really care about this, but I seem to recall that...

`6.0` _Preview 3_ is available with support for OData 8.0. I have a feeling this might work now.

`6.0` has officially been released. In terms of routing, if it works with vanilla OData 8.x+, then it should _just work_ with API Versioning. `6.0` will still support .NET Core...