Chris Martinez

It looks like this might finally be fixed in .NET 10: https://github.com/dotnet/aspnetcore/pull/54158 Due to the way the `IProblemDetailWriter` works, it's an unsafe assumption to decorate any registered instance. It's kind...

Yeah, I'm not in love with out the ASP.NET team designed out the writers get added. There's no concept of ordering, which makes the DI registration order matter and not...

Apologies for not replying to your last post. If I'm understanding what you're saying, the decorated/replaced writer should occur at the same index so that the order is retained? I'm...

This thread has gone quiet, but it's not dead. @domaindrivendev and I have talked it over. Ultimately, this is being held up by https://github.com/aspnet/Mvc/issues/7563, which demonstrates a gap in the...

Indeed this has happened in both the ASP.NET Core and API Versioning libraries. It does, however, require ASP.NET Core 2.2+. @domaindrivendev, I tried reaching out by email before the holidays....

You don't _have_ to. This class is providing bridge to fill in default values from the API Explorer. If you don't need that, things will work just fine. In addition...

@RehanSaeed does Swashbuckle support or otherwise use all of the relevant, provided metadata now? I was under the impression the answer is still no. If it does, then this issue...

@ericsampson it **is** _fixable_. There was a time when **IsOptional** was the wrong thing (it meant something different). There is now a **IsRequired** property on API descriptors. There is also...

@martincostello Wow! Time flies. Sadly, as far as I can tell, it is still relevant - if not at least in part. In the ideal state, combining Swashbuckle and API...

We _could_ create templates for the CLI and _possibly_ VS, but that would be a separate issue and feature request. That may be the happy bridge with Swashbuckle being removed...