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

📗 Learn from the written tutorial 👇👇 https://resocoder.com/proper-error-handling-2 🎯 The biggest Flutter conference in Europe: https://fluttereurope.dev 📧 Get Flutter news 📰 and resources: 👉 http://flutter.education 👨‍💻 Do you write good code? Find out now! https://resocoder.com/good-code-quiz 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: ● https://resocoder.com Follow me on social media: ● https://instagram.com/resocoder ● https://www.facebook.com/resocoder ● https://twitter.com/resocoder