-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Does FluentResults.Extensions.AspNetCore
include Problem Details?
#170
Comments
Thank your for the good feedback! I had a very short look at the problem details concept last november but then I ignored it to save some time because I wanted to release a first mvp version of the FluentResults.Extensions.AspNetCore package. If you see the need to use the ProblemDetails concept in this package you can try to integrate it and send an pr. Since November 2022 this asp.net core package have some thousands installs - so the interest is not that big in the community. I have to invest my time wisely. ;) |
@jeffward01 @altmann. I needed to add ProblemDetails too. This is what I did following the documentation. I'm using .Net7 On
This is the class
And here the
You can check here I hope this work for you. |
Hey guys, first version pushed. Goal here is domain(result)<->api-presentation(problemdetails). The glue in the middle: |
This looks interesting. Does this work with minimal APIs? |
@frasermclean now it work 😁 |
@altmann if you want I can PR my repo into yours (extensions). What you think? |
It would be very nice if the Result HTTP Response was in a common 'standard' format such as: ProblemDetails
I did not see ProblemDetails mentioned, so I thought I would ask
Very cool library!! I really love it.
Also I am working on a way to integrate it with CSharpFunctionalExtensions - the author of CSharpFunctionalExtensions seems to have inspired you to write FluentResults
The text was updated successfully, but these errors were encountered: