Refactor Riverpod usage to best practices#2
Conversation
- Updated `AuthController.build` to use `ref.watch` for dependencies, ensuring reactivity. - Inline `_checkTokenValidity` to explicit dependency tracking in `build`. - Updated `authLocalDataSourceProvider` and `authRepositoryProvider` to use `ref.watch` for their dependencies. - This aligns with Riverpod best practices to ensure providers rebuild when their dependencies change.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This PR refactors the Auth feature's providers to adhere to Riverpod best practices. Specifically, it replaces
ref.readwithref.watchinside provider bodies and thebuildmethod ofAsyncNotifier. This ensures that the providers are properly reactive and will rebuild if their dependencies (likesharedPrefsProviderordioProvider) change. It also refactorsAuthControllerto handle repository calls more explicitly within the reactive scope.PR created automatically by Jules for task 5129235174284695632 started by @GGNado