Functional Error Handling in Flutter & Dart (#2 – Either, Task, FP)

📗 Learn from the written tutorial 👇👇


🎯 The biggest Flutter conference in Europe:


📧 Get Flutter news 📰 and resources:
👉

👨‍💻 Do you write good code? Find out now!


From the first part, you already know that you shouldn't catch every exception with a blanket catch statement and you also learned how to get error messages over to your state management solution, such as a ChangeNotifer. Some may say "That's it!", but as proper software developers we should prefer hard rules over conventions.


Currently, we won't get any compile-time or even run-time errors when we don't display an error message to the user. Secondly, we treat error flow and "success data" flow separately - one through exceptions, another through return values. Similarly, we store the "success data" and its associated Failure in two distinct fields in the ChangeNotifier... Is there a way to join them?

Go to my website for more information, code examples, and articles:
●

Follow me on social media:
●
●
●

resocoder,tutorial,programming,code,programming tutorial,flutter,flutter tutorial,flutter exception handling,flutter exceptions,flutter error handling,flutter error,dart error handling,darts errors,dart exceptions,dart functional programming,dartz tutorial,