DeveloperExceptionMiddleware shouldn't have dependencies to ProblemDetails

[brunolins16]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

In #42212 was introduced the IProblemDetailsService and the DeveloperExceptionPageMiddleware updated to include ProblemDetails payload generation.

However, it introduced an unnecessary dependency to JsonOptions and ProblemDetails that could have been avoided if the the ProblemDetails generation was implemented using an IDeveloperPageExceptionFilter.

Expected Behavior

DeveloperExceptionPageMiddleware should not have dependencies to JsonOptions or ProblemDetails but should have the ProblemDetails payload generated when AddProblemDetails is called.

.NET Version

.NET 7

[captainsafia]

Triage: @mitchdenny As part of #46969, can you see if ProblemDetails is a big contributor to the size accounting for DeveloperExceptionPage? If it is a big contributor, we may consider doing this work.

[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.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mitchdenny]

Moving to backlog due to reprioritization.