apps/web/src/components/mentor/MentorExpandChatCard/hooks/useExpandCardClickHandler.ts (1)

28-40: 중복된 !isCheckedState 조건문

Lines 30-32와 33-39에서 !isCheckedState 조건을 두 번 체크하고 있습니다. 이를 하나로 합칠 수 있습니다.

♻️ 조건문 통합 제안

 const handleExpandClick = () => {
   setIsExpanded(!isExpanded);
-  if (!isCheckedState) {
-    setIsCheckedState(true);
-  }
-  if (!isCheckedState) {
+  if (!isCheckedState && clientRole) {
+    setIsCheckedState(true);
     if (isMentor) {
       patchCheckMentorings({ checkedMentoringIds: [mentoringId] });
     } else {
       patchMenteeCheckMentorings({ checkedMentoringIds: [mentoringId] });
     }
   }
 };

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@apps/web/src/components/mentor/MentorExpandChatCard/hooks/useExpandCardClickHandler.ts`
around lines 28 - 40, The handleExpandClick function currently checks
!isCheckedState twice; refactor by toggling expansion with
setIsExpanded(!isExpanded) then, in a single if (!isCheckedState) block call
setIsCheckedState(true) and invoke the appropriate API: if (isMentor) call
patchCheckMentorings({ checkedMentoringIds: [mentoringId] }) else call
patchMenteeCheckMentorings({ checkedMentoringIds: [mentoringId] }); keep the
same referenced symbols (handleExpandClick, setIsExpanded, setIsCheckedState,
isCheckedState, isMentor, patchCheckMentorings, patchMenteeCheckMentorings,
mentoringId).

apps/web/src/lib/zustand/useAuthStore.ts (1)

92-100: 2. setClientRole 가드 로직 - 빈 객체 반환 시 무음 실패

serverRole !== ADMIN일 때 빈 객체 {}를 반환하여 상태 변경 없이 조용히 무시됩니다. 이는 의도된 동작이지만, 디버깅 시 혼란을 줄 수 있습니다.

개발 환경에서 경고 로그를 추가하는 것을 고려해보세요:

💡 디버깅 편의를 위한 경고 로그 추가 제안

 setClientRole: (role) => {
   set((state) => {
     if (state.serverRole !== UserRole.ADMIN) {
+      if (process.env.NODE_ENV === "development") {
+        console.warn("[useAuthStore] setClientRole called but serverRole is not ADMIN");
+      }
       return {};
     }

     return { clientRole: role };
   });
 },

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/web/src/lib/zustand/useAuthStore.ts` around lines 92 - 100, The
setClientRole updater silently ignores attempts when state.serverRole !==
UserRole.ADMIN by returning an empty object; change it to emit a dev-only
warning so unauthorized attempts are visible: inside setClientRole (the function
using set and checking state.serverRole), detect the non-ADMIN case and call a
logger (e.g., console.warn or your app logger) with a clear message including
the attempted role and current serverRole, then return the unchanged state as
before; ensure the warning runs only in development (process.env.NODE_ENV !==
'production') to avoid noisy logs in production.

apps/web/src/components/layout/GlobalLayout/ui/AIInspectorFab/index.tsx (1)

22-22: 페이지 이동 시 메뉴 상태 초기화 고려

isMenuOpen 상태가 페이지 이동 후에도 유지될 수 있습니다. SPA 특성상 컴포넌트가 언마운트되지 않으면 메뉴가 열린 채로 남을 수 있습니다.

필요시 라우트 변경 감지하여 메뉴를 닫는 로직을 추가할 수 있습니다.

💡 라우트 변경 시 메뉴 닫기 (선택적)

import { usePathname } from "next/navigation";
import { useEffect } from "react";

// 컴포넌트 내부에서
const pathname = usePathname();

useEffect(() => {
  setIsMenuOpen(false);
}, [pathname]);

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/web/src/components/layout/GlobalLayout/ui/AIInspectorFab/index.tsx` at
line 22, isMenuOpen can persist across SPA route changes; add route-change
detection to automatically close the menu by using Next's usePathname and a
useEffect that calls setIsMenuOpen(false) whenever pathname changes (inside the
AIInspectorFab component where isMenuOpen and setIsMenuOpen are defined). Import
usePathname and useEffect, derive const pathname = usePathname(), and add
useEffect(() => setIsMenuOpen(false), [pathname]) to reset the menu on
navigation.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".