fix(auth): handle error properly in loadCurrentUser

Updated the loadCurrentUser function to throw specific errors when an API error occurs. This improves clarity and error handling, replacing the generic "No current user result" exception.
twentyhq · Jan 10, 2025 · 04e2f84 · 04e2f84
1 parent 5648c3b
commit 04e2f84
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/packages/twenty-front/src/modules/auth/hooks/useAuth.ts b/packages/twenty-front/src/modules/auth/hooks/useAuth.ts
@@ -177,12 +177,12 @@ export const useAuth = () => {
   const loadCurrentUser = useCallback(async () => {
     const currentUserResult = await getCurrentUser();
 
-    const user = currentUserResult.data?.currentUser;
-
-    if (!user) {
-      throw new Error('No current user result');
+    if (isDefined(currentUserResult.error)) {
+      throw new Error(currentUserResult.error.message);
     }
 
+    const user = currentUserResult.data?.currentUser;
+
     let workspaceMember = null;
 
     setCurrentUser(user);