Chris Martinez

@brunolins16 I just got a chance to revisit this. I was about to spin up the PR, but it looks like it has already been done and more so. 😄...

@akshaybheda Your setup is incorrect. I've provided the correct setup in #1096.

First up, I agree with @martincostello. We don't want to _hide_ duplicate types; it's a mistake. OpenAPI isn't meant to represent the concept of a _full-qualified_ name or _namespace_ as...

While it might not be the _right_ way or, at least, what I would do, it should be possible to do things however you want. My hunch seems to confirm...

@Angelinsky7 Your repro was helpful. There are a litany of problems, but I peeled back just the most relevant to get things working. In no particular order: - If you...

@glasody the reason this is happening is that you have split things across OData route prefixes. An OData route prefix does not define a sub application or segregation. The API...

Hey @captainsafia! Great to hear from you. Congrats on the release. Hope all is well. I'd love to help out with this. If there are any specific requirement, features, or...

I can't say that I know much about this framework, but I'm happy to help answer any questions related to API Versioning that can help you achieve your goals. Based...

In revisiting this for .NET 7, I think _there_ may be some possibility to improve things. In previous versions, it was assumed that candidates could simply be eliminated by API...

My preliminary research shows that I can collate _supported_ and _deprecated_ API versions as they are built up in the routing system. The metadata for each endpoint has already been...