How to customise the ProblemDetails object when capturing FluentValidation exceptions? about middleware HOT 5 OPEN

Hello @iaingymware! 👋

Have you looked at the sample in this repo? It shows a bunch of ways you can return custom problem details responses. You can return it directly from controllers, use Map functions when configuring the middle ware etc.

It's hard to give more specific feedback without knowing more details about what you want to achieve.

from middleware.

Hi @khellang

I am using your example here linked just below to capture the FluentValidation Validation Exception.

https://github.com/khellang/Middleware/blob/master/samples/ProblemDetails.Sample/ProblemDetailsOptionsExtensions.cs

This uses the ProblemsDetailFactory to generate a ProblemsDetails instance with errors. This works brilliantly however I want to customise the returned ProblemDetails instance.

Is there a way to use the sample Extension class however provide specific values, i.e Type, Title, Detail etc or do I need to write my own factory implementation similar to yours?

Thanks

from middleware.

If I'm not mistaken, the factory methods let you specify every single property of the problem details spec.

from middleware.

So I could use this, but it doesnt accept errors as a param:

Then we have this, but it accepts ModelStateDictionary (which i dont have as this is a web api) and no errors details:

This which accepts error and status code, but no other params:

and then this which is the same but an IDictionary version rather than SerializableError:

Sorry if I've missed something or I am mistaken, but I dont see a way to pass all custom ProblemDetails values, as well as the errors dictionary?

Thanks

from middleware.

Hi @khellang

Any update on how I should progress with this?

Thanks

from middleware.