Chris Martinez

I can't speak to what the OData team's examples do or don't support. If you want to see it working with API Versioning and OData query options in OpenAPI, then...

Great questions. >1. Where is this option used? This _should_ be useful in any scenario where `ProblemDetails` or `ProblemDetailsOptions` would be used to make a decision, which includes all of...

@brunolins16 ignoring options is always a possibility. Extenders don't have to honor the `JsonOptions` either. They might elect not to or don't realize they need to nor how (e.g. via...

@brunolins16 I agree - no need to over-engineer things. Rolling up things into the `DefaultProblemDetailsWriter` and making it extensible would be great. I suspect it would probably look like the...

@adityamandaleeka The primary work is settling on the the API design, which seems largely to be naming. The effort to execute is trivial IMHO and I'm happy to put the...

@source-studio I have confirmed that this is, in fact, a 🐞 . The current adapter logic is backward. It should be: ```c# if ( acceptHeaderValue.IsSubsetOf( jsonMediaType ) || acceptHeaderValue.IsSubsetOf( problemDetailsJsonMediaType...

cc @brunolins16

🤦🏽 Uggh.. you're so right. Duh?! That _sneaky_ `break;`🥷 It could still be simplified to: ```diff public ValueTask WriteAsync(ProblemDetailsContext context) { ArgumentNullException.ThrowIfNull(context); ArgumentNullException.ThrowIfNull(context.ProblemDetails); ArgumentNullException.ThrowIfNull(context.HttpContext); if (context.HttpContext.Response.HasStarted || context.HttpContext.Response.StatusCode < 400...

Sure. I can spin up a PR. What is gained (or retained) by keeping the branch for `if (_writers.Length == 1)`? Since `_writers_ supports indexing, I don't see any additional...

Updated the title to correctly reflect the proposed change