riverpod-mutations

Manage async form submission states in Riverpod using the experimental Mutation API to track loading, success, and error conditions independently of your main application state. It isolates UI-driven action states like MutationPending and MutationError.

Show UI feedback for data updates by handling MutationPending, MutationSuccess, and MutationError states. This approach allows you to directly display loading spinners, success confirmations, or error alerts tied to specific user actions.

Handle multiple async mutations on list items using keyed mutations in Riverpod. This feature supports distinct instances of the same operation, allowing you to manage concurrent data updates for individual entities separately.

Yes, you can track UI-driven operations separately using MutationIdle, MutationPending, MutationSuccess, and MutationError states. These specific states prevent async operation status from cluttering your primary data providers.

Riverpod supports isolated state tracking for concurrent user actions through the experimental Mutation API. You can run mutations for tasks like adding todo items while maintaining distinct success or error states for each action.

Use keyed mutations for state management in Riverpod when handling distinct operations across multiple entities, such as updating individual list items. This ensures separate tracking for concurrent actions without overlapping UI feedback.