I would like to know the best way to pass the bloc. I read about the bloc providers, but what`s the difference between using them and just passing the bloc in the constructor like:
ExampleView X = ExampleView(bloc,...)
Actually I find this way easier to test and also a better way to keep the code cleaner. For example, if I have more blocs, something like this can happen:
XBlocProvider(
bloc: XBloc,
child: YBlocProvider(
bloc: Y,
child: ZBlocProvider...
)
or maybe it's just my lack of knowledge. So, which ones are the benefits?
First, in main. dart, place an Article List BLoC above the material app to store the app's state. Put your cursor over the MaterialApp and press Option+Return (Alt+Enter on a PC). The IDE will bring up the Flutter widget menu.
Bloc is a design pattern created by Google to help separate business logic from the presentation layer and enable a developer to reuse code more efficiently. A state management library called Bloc was created and maintained by Felix Angelo.
The problem with this:
ExampleView X = ExampleView(bloc,...)
It only make sense if you use your bloc as normal class/provider with some Stream\ValueNotifier
. Otherwise it has some issues.
If it's global bloc, it's more exhausting way to pass it. You should use XBlocProvider
on top of MaterialApp
.
By the way, if it's global/top level bloc, you can do this:
XBlocProvider(
bloc: xBloc, // Singleton
child XPage,
...
This way, you can access this bloc from anywhere of the application and also you can listen
it.
If it's local bloc, because the way we listen Bloc
or ChangeNotifierProvider
via InheritedWidget
's updateShouldNotify
method, it doesn't make sense to pass as constructor
because you can't use it directly as you intended. You need to put that instance inside BlocProvider
and consume it again, so it's extra work.
https://api.flutter.dev/flutter/widgets/InheritedWidget/updateShouldNotify.html
To overcome multi nested BlocProvider
s you can use MultiProvider
or MultiBlocProvider
.
Example:
MultiBlocProvider(
providers: [
XProvider(...),
YProvider(...),
ZProvider(...),
],
child: someWidget,
)
There are multi ways to pass depends on your need but don't worry about InheritedWidget
because it's pretty fast and convenient way to obtain your XBlocProvider
.
At the end, try to comprehend every approach, I especifically suggest you to grasp this article:
https://www.didierboelens.com/2018/12/reactive-programming---streams---bloc---practical-use-cases/
You'll get the idea when to use bloc with provider or as a singleton or instantiate like your example etc.
The first difference is how you access your bloc from the widget.
bloc
implementation, you have obtain it via Provider
which extends InheritedWidget
using context
for example:final xBloc = Provider.of<XBloc>(context);
What's more when you wrap your bloc
with BlocProvider
then your bloc
's scope is limited to this widget's subtree so it can be only accessed by the BlocProvider
s descendants.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With