Hi @EngincanV,
noted, I will explore the ExceptionSubcriber. Thank you!
Hi @EngincanV, I understand that I can wrap each endpoint in a try-catch block to handle unexpected errors, but that would be time-consuming for us. Is there a way to centrally handle unexpected errors and return a specific error code and message?
How can I set an error code and override the default generic error message ("An internal error occurred during your request!") for the unexpected exceptions?
{ "error": { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null } }
Thank @maliming
Hi, After migrated to OpenIdDict, the response from discovery endpoints are logged into the log file which consuming a lot of disk space, is there a configuration to turn it off?
Hi, please ignore it. I have fixed it by updating the Theme LeptonX version as well:
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="3.2.0" />
noted. Let me upgrade it to 8.2.0.
Thank you
Hi @maliming, Yes, I have enabled the feature. Could you let me know when this feature was officially released?
I created a new project using version 8.0.2, but noticed that the feature is not available. Interestingly, my older project, also on version 8.0.2, includes it. I'm not sure why there's this discrepancy.