riverpod-patterns

Correct ref usage in Riverpod requires calling ref.watch inside the build method and ref.read inside event callbacks to prevent unnecessary rebuilds. This pattern ensures your providers maintain optimal lifecycle behavior.

AsyncValue handling in Flutter requires exhaustive checking for loading, data, and error states. Using AsyncNotifier patterns ensures you manage asynchronous operations robustly without creating fragile state management logic.

Scaffolding new Riverpod providers involves applying AsyncNotifier patterns and lifecycle best practices. Following these provider patterns during onboarding or refactoring ensures your Flutter state management remains robust.

Common Riverpod anti-patterns include improper ref usage, inconsistent AsyncValue handling, and fragile lifecycle management. Code reviews should enforce correct watch and read rules to avoid these frequent Flutter state management mistakes.

Riverpod linting helps enforce provider patterns by catching improper ref usage and inconsistent AsyncValue handling. Applying these linting rules during code reviews prevents fragile lifecycle management in Flutter applications.

Use AsyncNotifier in Flutter when your providers need exhaustive AsyncValue handling for loading, data, and error states. This pattern provides robust lifecycle management compared to basic providers for asynchronous operations.