flutter-bloc-feature-pattern

Structure a Flutter Bloc feature by generating a canonical event, state, and bloc file trio. Use freezed sealed unions for states to ensure compile-time exhaustive UI switch handling across loading, loaded, and failure scenarios.

Select bloc_concurrency transformers based on event semantics: use droppable to prevent duplicate processing, restartable to cancel in-flight fetches, and sequential to enforce strict ordering for mutating state operations.

Wire Flutter Bloc state updates by using BlocBuilder for full rebuilds, BlocSelector for fine-grained updates, and BlocListener for side effects like navigation or displaying snackbars without triggering widget rebuilds.

Yes, you can use HydratedBloc for local persistence by implementing JSON serialization and defining a stable storagePrefix to safely cache state locally and restore it across app restarts.

Missing UI switch cases occur when states are not defined as freezed sealed unions. Using freezed makes state matching compile-time exhaustive, forcing the UI to explicitly handle every initial, loading, loaded, and failure state.

You need freezed to scaffold scalable Bloc features because it generates sealed state classes, ensuring compile-time exhaustive switch handling and preventing incomplete UI rendering when adding new state variants.