Error flow: Result, Failure and the UI

0%

How an error travels between layers: when an exception is caught, why a Result is needed, how a Failure hierarchy is built, and what the user finally sees. This stage is built on Dart's sealed classes and exhaustive switch.

1. Exceptions vs Result: which one and why

error-handlingdartresult

2. The Result class: a sealed class and an exhaustive switch

error-handlingdartsealedresult

3. A Failure hierarchy: typed errors

error-handlingdomainsealedl10n

4. Result vs Either (fpdart)

error-handlingfpdarttrade-offs