Тэги:
#flutter #flutter_tutorial #flutter_bloc #flutter_bloc_tutorial #flutter_state_management #flutter_bloc_state_management #flutter_bloc_cubit #state_management_flutter #flutter_riverpod #flutter_riverpod_tutorial #flutter_getx #flutter_gtex_tutorial #flutter_course #learn_flutter #learn_flutter_bloc #learn_flutter_bloc_package #flutter_bloc_project #flutter_complete_course #flutter_bloc_course #bloc_tutorial_flutter #flutter_bloc_for_beginners #flutter_bloc_pattern_exampleКомментарии:
Finish it fasttt, im really appreciating this! Good job
ОтветитьWhy use abstract class for your events when dart now supports sealed classes? Disclaimer: I haven’t watched the video to the end yet incase you ended up swapping abstract class.
Ответитьis there a reason to not use external packages like flutter_bloc ?
ОтветитьYou're dragon keep going،
How about using enums to push events to sink instead of creating class , what is the purpose of creating class for events if there is no method or data inside it?
This is the best option without using any external packages. However, can we achieve functionality similar to Provider, where the same data can be updated in multiple screens? Do we need to declare a controller globally?
ОтветитьPlease finish this series first and then go for riverpod
Ответить