Unfortunately the website you used shut down their business and their website as well so I could only follow up to the 4 minute mark, there is no API page anymore.
Hello. Having an export file allows us to have one place where our classes, functions etc can be exposed to other files. If we do not do that, then we will have to import those files directly, which increases the amount of imports we will have across the codebase. Hope that makes sense
I'm currently converting a mature project from provider to riverpod, and in every two hours I still have working code, after converting one or two of the providers to riverpod. So yes, multiple state management systems can interop, but since riverpod can do everything bloc does with less boilerplate and more flexibility, the eventual goal would seem to be a gradual migration to being fully riverpod.
My answer is pretty much similar to Randal's. You can use more than one state management solution but it's not beneficial in the long run since you would have to context switch between both approaches, which can be mentally taxing. I would probably not use bloc directly but rather the dart_frog framework which integrates the bloc framework.
![FendiDa Rappa - Clock Dat ft. Shamar Marco [Official Music Video]](http://i.ytimg.com/vi/3NBU8KHdxYY/mqdefault.jpg)
Unfortunately the website you used shut down their business and their website as well so I could only follow up to the 4 minute mark, there is no API page anymore.
have you found any similar api?
is there any similar API we can test? the one used was shutdown
Hi, thanks for the video.
Why we use code generation feature? what are the benefits of it?
Awesome video on the standard Riverpod setup and how to use it with annotations 🙌🏾
can you add tutorial with riverpod hooks?
hi, i'm just a flutter beginner, i'm have question about why you need a wishlist.dart to export the path? what is this for? thank you.
Hello. Having an export file allows us to have one place where our classes, functions etc can be exposed to other files. If we do not do that, then we will have to import those files directly, which increases the amount of imports we will have across the codebase. Hope that makes sense
@@CreativeBracket got it, thank you sir
Can there be more than one state management solution on the server? For instance, bloc and riverpod
I'm currently converting a mature project from provider to riverpod, and in every two hours I still have working code, after converting one or two of the providers to riverpod. So yes, multiple state management systems can interop, but since riverpod can do everything bloc does with less boilerplate and more flexibility, the eventual goal would seem to be a gradual migration to being fully riverpod.
@@RandalLSchwartz thanks for your input
My answer is pretty much similar to Randal's. You can use more than one state management solution but it's not beneficial in the long run since you would have to context switch between both approaches, which can be mentally taxing. I would probably not use bloc directly but rather the dart_frog framework which integrates the bloc framework.