Skip to content

Migrate State Management to Riverpod #26

@breadoncee

Description

@breadoncee

Description:

The current app utilizes Provider for state management, but the implementation has grown complex and hard to maintain over time. To enhance code quality, scalability, and testability, I propose migrating the app's state management to Riverpod.

Reasons for Migration:

  • Provider Complexity: The existing codebase has become cluttered, making it difficult to manage and scale.
  • Improved Testability: Riverpod offers better testability by allowing fine-grained control over state and dependency management.
  • Cleaner Codebase: Riverpod encourages more structured and maintainable patterns, which will make future development smoother.
  • Performance Benefits: Riverpod offers performance optimizations by providing more efficient state updates and fine control over rebuilds.

Objectives:

  • Refactor existing state management to use Riverpod instead of Provider.
  • Ensure that the migration does not affect the current app’s functionality.
  • Write tests for state management to ensure behavior remains correct and is easier to maintain moving forward.
  • Clean up existing code to align with Riverpod’s best practices.

Metadata

Metadata

Assignees

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions