-
Notifications
You must be signed in to change notification settings - Fork 100
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] How to handle unsuccesful results at API level #171
Comments
@dkamau Are you using FastEndpoints? |
@KyleMcMaster Yes I am. |
We've discussed adding FastEndpoints support in issue #157 |
i using fast endpoit around six months on my work , i think it's a great idea add FE support to Results. I wanna participate |
There is work being done to provide support for FastEndpoints similar to the functionality for ASP.NET Core support. Consider 👍 'ing the issue in #175 if you'd like to see this implemented. |
See this comment from #175:
I'm assuming that either this fixes the immediate issue or, if not, that #175 will do so, so I'm going to close this now. Re-open if you still need to. |
For example, if I sent back a conflict from my handler;
return Result.Conflict($"Contributor with name {request.NewName} already exists!");
How will I report that to the user at the API level?
I tried this but it does not report as expected
The text was updated successfully, but these errors were encountered: