riverpod-faq-and-practices

ref.refresh and ref.invalidate are Riverpod methods for managing provider state. ref.invalidate marks a provider as dirty for re-initialization on next read, while ref.refresh immediately recreates the provider and returns its new state.

ConsumerWidget is used in Flutter when a widget needs to listen to or read Riverpod providers. Unlike StatelessWidget, ConsumerWidget provides a WidgetRef parameter, enabling direct access to provider states within the build method.

To avoid initialization side effects in Riverpod providers, you should adhere to best practices by keeping provider creation pure. Avoid triggering asynchronous operations or mutations directly within the provider's initialization body.

WidgetRef is used inside Flutter widgets to interact with providers, while Ref is used within other providers. Proper use of Ref versus WidgetRef ensures correct lifecycle management and prevents memory leaks in Riverpod.

Ephemeral state should be avoided in Riverpod providers to maintain predictable state management. Storing temporary UI state in providers causes unnecessary rebuilds and complicates lifecycle management, violating standard Flutter Riverpod best practices.