[API Proposal]: Add new constructor for `HttpValidationProblemDetails` that accepts a `IEnumerable<KeyValuePair<string, string[]>>`

[joegoldman2]

Background and Motivation

#41899 introduces new overloads for Results.ValidationProblem and TypedResults.ValidationProblem that accepts a IEnumerable<KeyValuePair<string, string[]>> for the errors.

For the sake of consistency, it would be good to have a constructor in HttpValidationProblemDetails that also accepts a IEnumerable<KeyValuePair<string, string[]>>.

More context: #41899 (comment)

Proposed API

namespace Microsoft.AspNetCore.Http;

public partial class HttpValidationProblemDetails : ProblemDetails
{
     // existing
     public HttpValidationProblemDetails()
     public HttpValidationProblemDetails(IDictionary<string, string[]> errors)

     // new
+    public HttpValidationProblemDetails(IEnumerable<KeyValuePair<string, string[]>> errors);
}

Usage Examples

var errors = new List<KeyValuePair<string, string[]>> { new("testField", new[] { "test error" }) };
var problemDetails = new HttpValidationProblemDetails(errors);

Risks

Nothing I can see now.

[dotnet-policy-service]

Thank you for submitting this for API review. This will be reviewed by @dotnet/aspnet-api-review at the next meeting of the ASP.NET Core API Review group. Please ensure you take a look at the API review process documentation and ensure that:

• The PR contains changes to the reference-assembly that describe the API change. Or, you have included a snippet of reference-assembly-style code that illustrates the API change.
• The PR describes the impact to users, both positive (useful new APIs) and negative (breaking changes).
• Someone is assigned to "champion" this change in the meeting, and they understand the impact and design of the change.

[amcasey]

API Approved!