Error handling in clean architecture

[Norbert Nemes]

Hello everyone.

I'm curious if and how any of you implement error handling in clean architecture.

If an error happens in the Entities/interactors, do you cascade it back to the view?

Or do you have a "global" error manager?

Regards,

Norbert.

[vivek poddar]

+1

--
The only way to go fast is to go well.
---
You received this message because you are subscribed to the Google Groups "Clean Code Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clean-code-discu...@googlegroups.com.
To post to this group, send email to clean-code...@googlegroups.com.
Visit this group at http://groups.google.com/group/clean-code-discussion.

[Łukasz Duda]

Hi Norbert,
I usually implement global error handling outside application (at MVC controller level). The simple solution is to log all errors and return response without error details (for security reasons). The client recognises response and shows common error message. If the error is expected in some situation, the application can handle it or show appropriate message through responder instead throwing exception.
If you're interested, I could publish an example?

Greetings from hard-working Warsaw

[Norbert Nemes]

Yes, please.

I have a global manager in mind to which the (entities and) interactors would push errors and the manager would call back to the currently active presenter and ask if it handles the type of error it received, and if it does, it sends it the error. But I would like to see how others do this, maybe I get a better idea,

[Łukasz Duda]

I've published some examples of my approach to handling errors in .NET.
https://github.com/lukasz-duda/ErrorHandling
https://github.com/lukasz-duda/ErrorHandling/commit/bdb54f8e427213d8f7bed0c797afc525fb7304d9 - comments
Let me know if you have some questions or comments.

[Elias Fofanov]

The topic of errors handling via exceptions is an interesting and extremely important one.

Are there any approaches to designing the politics of exception types creating and handling them?

For example, should we create our own types of exceptions by layers, say, IDbException, IDomainException, e.t.c.? Or, maybe, we should design it somehow else?

[Tomer Ben David]

Have a look at this post: https://tersesystems.com/2012/12/27/error-handling-in-scala/  it kind of bring some order into when to use exceptions, when return values etc.