You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IExceptionToErrorInfoConverter interface and it's implementation are in the Volo.Abp.ExceptionHandling package (which targets netstandard2.0).
It's misleading that the components are inside the Volo.Abp.AspNetCore.ExceptionHandling namespace since it can be used on all platforms (wpf, winforms, you name it).
I can contribute a PR which refactors the namespace if it's ok. I just wanted to discuss this idea first.
The text was updated successfully, but these errors were encountered:
Great, I'll contribute a PR in the upcoming days. 👍
How should I deal with AbpExceptionHandlingOptions?
The property names (SendExceptionsDetailsToClients for example) can be refactored to IncludeExceptionsDetails and IncludeStackTrace.
Should I rename them too (breaking change), implement aliases (compatible properties) or leave them as they are (will update the Docs too)?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi,
The
IExceptionToErrorInfoConverter
interface and it's implementation are in theVolo.Abp.ExceptionHandling
package (which targets netstandard2.0).It's misleading that the components are inside the
Volo.Abp.AspNetCore.ExceptionHandling
namespace since it can be used on all platforms (wpf, winforms, you name it).I can contribute a PR which refactors the namespace if it's ok. I just wanted to discuss this idea first.
The text was updated successfully, but these errors were encountered: