A collection of packages that help implement the BLoC design pattern - https://felangel.github.io/bloc
:zzz:
Hello @felangel, thanks a lot for your library. I have the same problem like felangel/bloc#394
I don't know what I should do. For example. Usecase: create a new entity. I have a scaffold which has button and some body. When I press button I wanna to show progress on button. What I do now. I added stream to my block which responses for button state. Or I must create State which has a button state and body state. What I should do when happened failure?
I don't know what I should do. For example. Usecase: create a new entity. I have a scaffold which has button and some body. When I press button I wanna to show progress on button. What I do now. I added stream to my block which responses for button state. Or I must create State which has a button state and body state. What I should do when happened failure?
Hi All,
Is there anyway to provide the Bloc back when navigation back button is pressed?
I'm trying to implement authentication with SMS code, and here is the problem I'm facing.
Page 1 - page where user can enter phone number - when submitted, it dispacthes an event to validate the phone number, if all OK I have a BlocListener to navigate to Page 2 providing the bloc)
Page 2 - it's the page where user enters SMS code, if I hit navigation back in this page I can't submit the phone number again with the following error "Bad state: Cannot add new events after calling close"
@rlfrenato that means you’re disposing the bloc incorrectly. Are you using BlocProvider to create the bloc instance?
when on the main screen, it doesn't refresh/restart state on navigator.pop
SplashScreen widget is not showing
(following the firebase_login tutorial)
Hey guys! novice question about good practice for state management.
When using bloc, should the widgets they serve typically always be stateless? (excluding situations like animations where stateful is needed)
For example, I have a sign in page that requires data from an API, and I want the UI to be responsive so that loading, loaded, etc all have their own renders based on states provided from the bloc.
My question is, once the sign in screen is rendered, is it okay to store the username, password, etc. in the state of the stateful widget, and then dispatch them to the bloc all at once as arguments to the event, or should I try to store all user input in my same bloc?
When using bloc, should the widgets they serve typically always be stateless? (excluding situations like animations where stateful is needed)
For example, I have a sign in page that requires data from an API, and I want the UI to be responsive so that loading, loaded, etc all have their own renders based on states provided from the bloc.
My question is, once the sign in screen is rendered, is it okay to store the username, password, etc. in the state of the stateful widget, and then dispatch them to the bloc all at once as arguments to the event, or should I try to store all user input in my same bloc?
I would recommend passing the data like usernames and passwords to the bloc via events you dispatch
Did you take a look at the login tutorial?
In most cases you should not need a StatefulWidget
some bloc structure question
I have implemented item list with custom filtering
but I put all the filter elements inside the same bloc
should I separate them by two bloc like filterBloc & transactionBloc?
@dominwong4 it’s up to you. Mostly depends on if you’re going to need to consume both the raw and filtered in different parts of your app. If yes, then I’d recommend splitting the filtering into a separate filtered bloc otherwise it might be overkill if the raw transactions won’t be consumed
if the error still persists, read this: https://github.com/flutter/flutter/issues/25640#issuecomment-449589417
thanks