Chris Martinez

@fannydengdeng some initial questions: 1. Which version of API Versioning are you actually using? a. You cited `4.1`, which is very old (in software age 😉) 2. Is there some...

@fannydengdeng, The common thing that can cause re-entry into the routing system is a variance of route constraints in the route templates between API versions. For example, if you had...

>Question: is it expected that route template is "{*odataPath}" for all the routes? Yes. OData < 8.0 uses its own matching process and routing conventions. ASP.NET Core sees this as...

After digging into this more, I understand what is happening. Apologies for not reading the OP more carefully. The issue was outlined pretty clearly. @xuzhg The issue is related to...

I do not think this applies to types that use `*.proto` files because they simply would not be code-generated. I have a use case where I want to model a...

I'm open to possibilities, but I'd imagine rules similar to `serde`. 1. The field must support `Default`, which works for any primitive and recursively, in particular, for `Option` 2. Support...

_Fallback_ and _backward compatible_ are fallacies and a bad idea. It's almost always ends badly for the client. I've just added additional feedback to discussion #971. The only provided method...

This is good, I _think_. 😉 Let me try to play back what you want. Your APIs have symmetrical versions from the client's perspective. If you are on `2025-01-01` all...

A couple of things. First, I guess I forgot that `IApplicationModelProvider` does have an order - yay. Better still, I apparently did have the foresight to think that someone _might_...

That's correct, but `IControllerNameConvention` controls exactly how it gets generated. The default will be `ExampleController`, `Example1Controller`, and `Example2Controller` will all have the _group name_ of `Example`. This is how all...