Hi, Thank you for your reply. I tried your suggestion but I keep getting the exact same error.
Raffee
Hi again, Actually here is the JSON we are getting from the server:
{"result":null,"targetUrl":null,"success":false,"error":{"code":0,"message":"An internal error occurred during your request!","details":null,"validationErrors":null},"unAuthorizedRequest":false,"__abp":true}
We already disabled the automatic ABP error handling on the client, and we implemented our own, but we still don't have the details to work with. I could be wrong, but I believe we need a setting to tell the server to send us all the validation details instead of a generic "An internal error occurred during your request!" message.
Thanks, Raffee
Hi, Thank you for the quick reply :) We do have client side validation of course, but we also have server side validation, and we prefer to have as much detailed control as possible over what is displayed to the clients. I will try your suggestion and get back to you.
Regards, Raffee
Hi, I have a need to display validation error details to the user (PL). We don't want to stop the automatic validation based on data-annotations, which works great, but it seems to be sending a generic exception, which is displayed on the client side as "Internal Error Happened". So I was wondering if there is a way to force the internal validation to throw a User Friendly Exception, so that we can display the detailed message to the user.
Thanks! Raffee
Hi, I'm facing this same issue, but not in the test classes.
I want to create a custom exception type that contains a localized error message (specific to the exception, and not injected from outside). But when I try to resolve the ILocalizationManager interface I get an error that it is not implemented.
Hi, Following up with this question: how to use the custom repository in my domain services? Do you think it's OK to have cyclical references between .Core and .EntityFramework projects?