consume-effect

To consume one-time effects safely during the build phase, use `context.effect()` to read `Effect<T>` fields and mark them as spent. This prevents side effects like showing snackbars or navigating from re-triggering on widget rebuilds.

The best way to handle one-time events from a Cubit is by emitting `Effect<T>` fields from the state and consuming them in the UI using `context.effect()`, ensuring the navigation or dialog is triggered only once per event.

You read and mark a state effect as spent by accessing it via `context.effect()` in your widget's build method. This method reads the new value and automatically marks the effect as spent to prevent multiple triggers.

Yes, you can handle multiple one-time effects from different Cubits simultaneously. The `context.effect()` pattern safely manages and consumes distinct `Effect<T>` fields across multiple Cubit states within the same widget build.

Side effects trigger repeatedly because standard state variables are re-read on every build. Fix this by using `context.effect()` to consume the `Effect<T>` field, which marks it as spent after the first read.