Wow, this tutorial is an absolute lifesaver for anyone diving into Flutter development! 🚀 The BEST WAY for Error Handling in Flutter explained in such a clear and concise manner. Huge thanks to the talented creator for breaking down the complexities and making it so accessible for us. 🙌 Your commitment to helping the Flutter community grow is truly appreciated. Keep up the fantastic work, and I'm looking forward to more invaluable insights! 🌟 #FlutterDev #ErrorHandling #GratefulDeveloper"
Great tutorial! So that was the logic part. I am also wondering about the UI part. Like what are the best practices? Displaying the error every time is 1) useful but 2) annoying for the user. Also, we have to localize errors if we really display each of them. I think most errors should log directly against the backend and the developer should be informed automatically. But when that’s not possible we need a custom error message with translation. And should we ever retry fetching the api again or should the user always have to refresh the page themselves?
I agree both the packages are great for functional programming and dartz is not updated for over 2 years. So any of the package can be used for this. Dartz is more used I feel and has 1.2k likes as compared to fpdart which has 633. But fpdart is a good choice too if someone is familiar with that....
Lovely man lovly content 😊😊
Wow, this tutorial is an absolute lifesaver for anyone diving into Flutter development! 🚀 The BEST WAY for Error Handling in Flutter explained in such a clear and concise manner. Huge thanks to the talented creator for breaking down the complexities and making it so accessible for us. 🙌 Your commitment to helping the Flutter community grow is truly appreciated. Keep up the fantastic work, and I'm looking forward to more invaluable insights! 🌟 #FlutterDev #ErrorHandling #GratefulDeveloper"
Thanks so much for the kind words, means a lot. I am glad the video's helpful for other developers 😊
Great tutorial! So that was the logic part. I am also wondering about the UI part. Like what are the best practices? Displaying the error every time is 1) useful but 2) annoying for the user. Also, we have to localize errors if we really display each of them. I think most errors should log directly against the backend and the developer should be informed automatically. But when that’s not possible we need a custom error message with translation. And should we ever retry fetching the api again or should the user always have to refresh the page themselves?
any reason why you used dartz instead pf fpdart? fpdart is well documented and maintained, dartz is pretty much abandoned
I agree both the packages are great for functional programming and dartz is not updated for over 2 years. So any of the package can be used for this. Dartz is more used I feel and has 1.2k likes as compared to fpdart which has 633. But fpdart is a good choice too if someone is familiar with that....