Hi, great explanation! thks! I am using flutter_bloc, but no provider widgets at all. I use get_it to create and register all the instances and pass it to the bloc argument on the BlocBuilder and BlocListener. This way I am widget and context independent, which helps especially when routing. Still, you have to manage the closing of the bloc stream yourself, which otherwise is handled for you through the providers. what do you think of tis approach? thks👍
thanks for good videos , but i still confuse what is the main function of RepositoryProvider? what the difference between RepositoryProvider and blocprovider ?
Thanks a lot. I understood. However, can you please, while recording your videos, increase your audio level. I just could not hear you clearly. I had to increase the volume to 80%. thanks a lot.
"Thanks for the video. However, I'm still a bit confused about the practical use of RepositoryProvider. Could someone help clarify whether I understood it correctly or not? Suppose I want to use flutter_bloc in a weather app. When the user triggers an event to get the weather for a particular location, my understanding is that instead of fetching data directly from the API within the bloc class, we would trigger (or call) a method from our repository class. Based on the result obtained, we'll then update the state. Is this the correct usage of RepositoryProvider in this scenario? Any insights would be greatly appreciated!"
Well, first of all we need to know why we used a repository. Using a repository in software architecture helps separate concerns by defining how data is fetched from remote or local sources within the data layer, rather than directly from the bloc. We could create a repository's instance inside the bloc but this will create another dependency between the bloc and the repository, so we inject the repository through the constructor of the bloc. Instead of creating multiple instances or using a third-party library like get_it, we can use RepositoryProvider to instantiate the repository once and pass it through the context, allowing the repository to be accessed when needed.
It's so hard to understand all the multitude of patterns used in a simple app. Maybe that's why it's so difficult for Flutter to take its seat. I looked for so long for an updated tutorial that encompassed: fetch data from external source (firebase is a good one, or any api), have it stored locally, and relay this data on to widgets. I've only seen parts of this and it's not manageable. Some tutorials teach bloc, others providers, some simple widgets, some local storage and some Dio, but not one of them employ the full solution. :(
Hi, great explanation! thks! I am using flutter_bloc, but no provider widgets at all. I use get_it to create and register all the instances and pass it to the bloc argument on the BlocBuilder and BlocListener. This way I am widget and context independent, which helps especially when routing. Still, you have to manage the closing of the bloc stream yourself, which otherwise is handled for you through the providers. what do you think of tis approach? thks👍
thanks for good videos ,
but i still confuse what is the main function of RepositoryProvider?
what the difference between RepositoryProvider and blocprovider ?
for get data from api it is possible right with only use bloc ?
yes, you can but you should only trigger events in bloc, not really do other things.If you load data from bloc, your code will soon get messy.
Thanks a lot. I understood. However, can you please, while recording your videos, increase your audio level. I just could not hear you clearly. I had to increase the volume to 80%.
thanks a lot.
"Thanks for the video. However, I'm still a bit confused about the practical use of RepositoryProvider. Could someone help clarify whether I understood it correctly or not?
Suppose I want to use flutter_bloc in a weather app. When the user triggers an event to get the weather for a particular location, my understanding is that instead of fetching data directly from the API within the bloc class, we would trigger (or call) a method from our repository class. Based on the result obtained, we'll then update the state.
Is this the correct usage of RepositoryProvider in this scenario? Any insights would be greatly appreciated!"
Well, first of all we need to know why we used a repository. Using a repository in software architecture helps separate concerns by defining how data is fetched from remote or local sources within the data layer, rather than directly from the bloc. We could create a repository's instance inside the bloc but this will create another dependency between the bloc and the repository, so we inject the repository through the constructor of the bloc.
Instead of creating multiple instances or using a third-party library like get_it, we can use RepositoryProvider to instantiate the repository once and pass it through the context, allowing the repository to be accessed when needed.
@@BrunoMazzocchi Thanks
In ur authstate why are overriding list??
what happens if we directly give AuthRepository() to the BlocProvider instead of using RepositoryProvider() ?
If you don't do using RepositoryProvider(), you would load the data, from initState() or other kind of mechanism. Or using an event
@@dbestech is it fine if we don't use the RepositoryProvider()?
@@bhuvanachandra5121 you can skip that, but in that case we need to load the repos differently
can we get the whole authentication video with bloc?
yes, I recorded half. I am too busy. maybe tomorrow release
@@dbestech okk , thanks
can we also use bloc builder in place of stream builder in above example?
StreamBuilder would help you to know auth changes about firebase auth
BlocBuilder would not do it
Why not connect the data layer to the repository class?
We can do that as well
Thank you. Great session! Could you share the source code?
The code is not complete yet
Nice explanation
Thanks for liking
It's so hard to understand all the multitude of patterns used in a simple app. Maybe that's why it's so difficult for Flutter to take its seat.
I looked for so long for an updated tutorial that encompassed: fetch data from external source (firebase is a good one, or any api), have it stored locally, and relay this data on to widgets.
I've only seen parts of this and it's not manageable.
Some tutorials teach bloc, others providers, some simple widgets, some local storage and some Dio, but not one of them employ the full solution. :(
sorry, you may ask questions to me.
Hello, im looking for a flutter developer who is good with bloc and state management for a project
freelancing?
@@dbestech yes! If you could help that would be nice!
You’re the goat 🐐
❤️❤️