Brian Engen

for anyone else following along, I'm developing my web components with Vue3 and am able to work around this with the following added to my top-most component. would be great...

My fork has fallen behind master so there are some merge conflicts now. My day job keeps me pretty busy but I should have some time this weekend to get...

Quick update - I just added `app.UseODataRouteDebug();` and can confirm that my endpoints aren't being mapped as odata endpoints. I'm experimenting with different options, but I'd be grateful for any...

To follow up with where I've landed: It seems that the odata framework is only mapping my controller endpoints if they follow odata routing conventions. I thought this wasn't necessary...

thanks for the suggestion, but using `ODataController` doesn't result in any different result. the "issue" is right [here](https://github.com/OData/AspNetCoreOData/blob/4f537fa77c2a2de7f60118850c0f017660cff578/src/Microsoft.AspNetCore.OData/Routing/Conventions/AttributeRoutingConvention.cs#L265), I think. on that line of code, my `routeTemplate` is `"sample/v{version:apiVersion}/Users"` and...

if anyone is wanting this same capability, I've put together a project that will hopefully be helpful to others. pretty simple adaptation of the `AttributeRoutingConvention` to expand out the action...

I've updated my repo (linked above) to a "working state" with API versioning and a brute-force example for ApiExplorer/swagger support that I may improve later if I have time. ways...

The value (at least, for me) is I can load my configuration from json, azure app config service, or any other supported configuration sources, bind that config to objects, and...