[AOT] ProblemDetails and Extension values

[JamesNK]

Problem Details is an internet standard - https://www.rfc-editor.org/rfc/rfc7807

In ASP.NET Core, ProblemDetails is serialized with IProblemDetailsWriter. The default implementation is DefaultProblemDetailsWriter.

One of the concepts of problem details is extension data. These are arbitrary values that can be added to the payload. This is difficult with AOT because it's represented on ProblemsDetails as IDictionary<string, object>. Serializing problem details successfully (don't worry about deserializing, aspnetcore doesn't do that) means all the values in the directory must have generated code registered with the serializer.

[JamesNK]

ProblemDetails.Extensions is annotated to warn that types set in it are serialized, and that there maybe problems with serializing because values aren't able to be statically analyzed.

If there are changes to remove ProblemDetails.Extensions warning, then make sure to remove suppressions that come from using it. Right now, that is DeveloperExceptionPageMiddlewareImpl.

[halter73]

Triage: We want to try to remove the annotations ProblemsDetails.Extensions possibly by flowing the user's JsonTypeInfo registrations when serializing ProblemDetails.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[brunolins16]

@JamesNK I believe this issue was fixed by #45886 as #45906, right?

[JamesNK]

Yup