fix(auth): refactor initializeAuth for improved token handling and us… - #191
Merged
Conversation
…er state management
salehahmed99
approved these changes
Dec 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request refactors the authentication initialization logic in
useAuthStoreto improve error handling and code clarity. The main change is restructuring the logic to handle errors in a more centralized way, reducing code duplication and ensuring that cleanup steps are consistently applied.Authentication flow improvements:
initializeAuthlogic in a singletry-catch-finallyblock to centralize error handling and ensure that tokens and user state are always properly reset on failure. [1] [2]try-catchblocks and simplified the logic for handling invalid tokens and refresh tokens, reducing code duplication and potential inconsistencies.isInitializedstate is always set totruein afinallyblock, guaranteeing that the app knows initialization is complete regardless of success or failure.…er state management