I've been experimenting with Riverpod a lot the last couple weeks and am now ready to try it in a greenfield project I've been meaning to write for some time. In lieu of a good design patterns/best practices book (if one exists I haven't found it anyway) I've been doing as best homework I can with finding videos/blog posts and little side experiments. One thing I discovered earlier this week was nested providers which I was thinking I may want to use to replace another idiom I had been using of having a provider that takes an item ID. Based on this presentation by @randalschwartz it sounds like that is not the way to go. In the video he does show how to do various scoping, both literal scope and logical scope, of providers in Riverpod. #riverpod#flutter#DartLang The Riverpod "Global" Myth
I've avoided using stuff like Freezed because the code generation aspects of Dart/Flutter don't integrate seamlessly with the IDE like I had with Java/Kotlin equivalents. Now that I've done a deep dive on trying to learn Riverpod it seems that code generation really helps make Riverpod a lot easier to work with. If I stick with RIverpod maybe that'll be what finally brings me over on using gen tools like Freezed too #DartLang#Flutter#programming#Riverpod