src/pages/admin/assignments/AssignmentFormPage.tsx (2)

117-134: 배열 인덱스를 key로 사용하면 리렌더링 이슈가 발생할 수 있습니다.

테스트케이스가 삭제되거나 순서가 변경될 경우, 인덱스 기반 key는 React의 reconciliation을 혼란시킬 수 있습니다. 고유한 ID를 사용하거나, 항목 추가 시 고유 ID를 생성하는 것을 권장합니다.

♻️ 개선 예시 (nanoid 또는 uuid 사용)

+import {nanoid} from 'nanoid';

-const [testcases, setTestcases] = useState([{testcase: '', answer: ''}]);
+const [testcases, setTestcases] = useState([{id: nanoid(), testcase: '', answer: ''}]);

 const handleAddTestcase = () => {
-  setTestcases([...testcases, {testcase: '', answer: ''}]);
+  setTestcases([...testcases, {id: nanoid(), testcase: '', answer: ''}]);
 };

 // In JSX:
-<TestcaseRow key={idx} ...
+<TestcaseRow key={tc.id} ...

React 공식 문서 참고: Lists and Keys

🤖 Prompt for AI Agents

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

In `@src/pages/admin/assignments/AssignmentFormPage.tsx` around lines 117 - 134,
The list is using the array index as the React key which can break
reconciliation when items are reordered or removed; update the TestcaseRow
mapping to use a stable unique identifier (e.g., testcase.id) instead of idx as
the key, and ensure new testcases created via whatever function adds to the
testcases state (the code paths that call setTestcases) generate and attach a
unique id (nanoid/uuid or incrementing id) to each testcase object so
TestcaseRow, onTestcaseChange and onAnswerChange continue to locate and update
items by id rather than by index.

---

144-148: FileUpload의 onFileChange 콜백이 비어 있습니다.

현재 빈 함수가 전달되어 파일 업로드 기능이 동작하지 않습니다. 추후 구현 예정이라면 TODO 주석을 추가하는 것이 좋습니다.

 <FileUpload
   label='테스트 케이스'
-  onFileChange={() => {}}
+  onFileChange={() => {}} // TODO: 파일 업로드 처리 구현 필요
   className='mb-9'
 />

🤖 Prompt for AI Agents

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

In `@src/pages/admin/assignments/AssignmentFormPage.tsx` around lines 144 - 148,
The FileUpload component is passed an empty onFileChange handler so uploaded
files aren't processed; implement a handler in AssignmentFormPage that accepts
the file or FileList from FileUpload's onFileChange and either updates local
state (e.g., setTestCaseFile) or updates the form state (e.g.,
formik.setFieldValue('testCases', files)), and pass that function to FileUpload,
or if you intentionally leave it unimplemented add a TODO comment explaining the
planned behavior; reference the FileUpload component and its onFileChange prop
in AssignmentFormPage to locate where to add the handler.

Fix all unresolved CodeRabbit comments on this PR:

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

src/shared/ui/ConfirmModal.tsx (2)

24-28: Dialog 내부 클릭 시 이벤트 버블링 방지 필요

backdrop 클릭으로 닫기를 구현할 경우, dialog 내부 클릭이 backdrop으로 전파되지 않도록 해야 합니다.

🔧 수정 제안

      <section
        role='dialog'
        aria-modal='true'
        aria-labelledby='confirm-modal-title'
-       className='bg-white rounded-2xl p-8 w-80 flex flex-col gap-6 shadow-lg'>
+       className='bg-white rounded-2xl p-8 w-80 flex flex-col gap-6 shadow-lg'
+       onClick={(e) => e.stopPropagation()}>

🤖 Prompt for AI Agents

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

In `@src/shared/ui/ConfirmModal.tsx` around lines 24 - 28, The dialog's inner
section (the element with role='dialog' and
aria-labelledby='confirm-modal-title' in ConfirmModal) needs to stop click event
propagation so clicks inside don't trigger the backdrop close; add an onClick
handler on that section (or its top-level dialog container) that calls
event.stopPropagation() to prevent bubbling to the backdrop click handler,
keeping the existing backdrop onClick logic intact.

---

12-47: 접근성 개선이 필요합니다: 포커스 트랩 및 ESC 키 핸들링

모달이 열릴 때 포커스가 모달 내부에 갇히고, ESC 키로 닫을 수 있어야 합니다. 현재 구현에서는 사용자가 Tab으로 모달 외부 요소에 접근할 수 있습니다.

🔧 ESC 키 핸들링 추가 예시

+import { useEffect, useRef } from 'react';

 export default function ConfirmModal({
   // ...props
 }: ConfirmModalProps) {
+  const dialogRef = useRef<HTMLElement>(null);
+
+  useEffect(() => {
+    const handleKeyDown = (e: KeyboardEvent) => {
+      if (e.key === 'Escape') onCancel();
+    };
+    document.addEventListener('keydown', handleKeyDown);
+    dialogRef.current?.focus();
+    return () => document.removeEventListener('keydown', handleKeyDown);
+  }, [onCancel]);
+
   return (
     // ...
+      <section
+        ref={dialogRef}
+        tabIndex={-1}
+        role='dialog'
         // ...

참고: WAI-ARIA Modal Dialog Pattern

🤖 Prompt for AI Agents

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

In `@src/shared/ui/ConfirmModal.tsx` around lines 12 - 47, ConfirmModal lacks a
focus trap and ESC handling; update the ConfirmModal component to (1) store the
previously focused element when the modal mounts and restore focus when it
unmounts, (2) set initial focus to the modal container or the first focusable
button (use a ref like modalRef), (3) add a keydown listener on mount that
closes the modal when Escape is pressed by calling onCancel, and (4) implement
Tab/Shift+Tab trapping within the modal by preventing focus from escaping the
first/last focusable elements inside modalRef; also clean up listeners on
unmount. Use ConfirmModal, modalRef, onCancel and onConfirm identifiers to
locate where to add useEffect and ref logic.

eslint.config.js (1)

59-81: boundaries/entry-point 규칙이 'off'인데 상세 설정이 있습니다.

규칙이 비활성화되어 있어 하위 설정(rules 배열)이 적용되지 않습니다. 의도적으로 비활성화한 것이라면 주석으로 이유를 명시하거나, 규칙을 활성화하려면 'error' 또는 'warn'으로 변경하세요.

// 활성화하려면:
'boundaries/entry-point': [
  'error',  // 'off' → 'error' 또는 'warn'
  { rules: [...] }
]

🤖 Prompt for AI Agents

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

In `@eslint.config.js` around lines 59 - 81, The 'boundaries/entry-point' rule is
currently set to 'off' while still providing a rules configuration block, so
either enable the rule or remove/annotate the dead config; update the
'boundaries/entry-point' entry from 'off' to 'error' or 'warn' if you intend the
rules to apply (keeping the existing rules array), or leave it 'off' and add a
brief comment explaining why it's disabled or remove the nested rules entirely;
target the 'boundaries/entry-point' config block in eslint.config.js to make
this change.

src/widgets/assignment-form-layout/ui/AssignmentFormLayout.tsx (1)

4-13: 코딩 가이드라인: 객체 타입에는 interface 사용 권장

가이드라인에 따르면 "interface는 객체 타입, type은 union/alias에 사용"합니다. AssignmentFormLayoutProps는 객체 타입이므로 interface로 변경을 고려해보세요.

♻️ 선택적 리팩터링

-type AssignmentFormLayoutProps = {
+interface AssignmentFormLayoutProps {
   title: string;
   titleExtra?: React.ReactNode;
   content: React.ReactNode;
   onCancel: () => void;
   onConfirm: () => void;
   cancelLabel?: string;
   confirmLabel?: string;
   confirmDisabled?: boolean;
-};
+}

As per coding guidelines: "interface는 객체 타입, type은 union/alias에 사용"

🤖 Prompt for AI Agents

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

In `@src/widgets/assignment-form-layout/ui/AssignmentFormLayout.tsx` around lines
4 - 13, AssignmentFormLayoutProps is declared with a type alias but your coding
guideline requires using interface for object shapes; change the declaration of
AssignmentFormLayoutProps from a type to an interface (keeping the same property
names: title, titleExtra, content, onCancel, onConfirm, cancelLabel,
confirmLabel, confirmDisabled), ensure any existing imports/exports and
references (e.g., in AssignmentFormLayout component props) are updated to use
the new interface name, and run a quick type-check to fix any places where
union/alias-specific syntax was mistakenly used so the interface compiles
cleanly.

src/features/course/filter-course/lib/useCourseFilter.ts (1)

41-47: 역방향 조회 로직은 동작하지만, 개선 여지가 있습니다.

현재 courseOptionMap.entries()를 순회하여 label을 찾습니다. 강의 수가 적어 성능 영향은 미미하지만, 양방향 Map을 유지하면 O(1) 조회가 가능합니다.

♻️ 선택적 개선안

 const courseOptionMap = useMemo(() => {
   const map = new Map<string, number>();
+  const reverseMap = new Map<number, string>();

   courses.forEach((course) => {
     const label = formatCourseOptionLabel(
       course.title,
       course.year,
       course.semester,
       course.section
     );
     map.set(label, course.id);
+    reverseMap.set(course.id, label);
   });

-  return map;
+  return { labelToId: map, idToLabel: reverseMap };
 }, [courses]);

 const selectedCourseLabel = useMemo(() => {
   if (selectedCourseId === null) return ALL_COURSES_OPTION;
-  for (const [key, value] of courseOptionMap.entries()) {
-    if (value === selectedCourseId) return key;
-  }
-  return ALL_COURSES_OPTION;
+  return courseOptionMap.idToLabel.get(selectedCourseId) ?? ALL_COURSES_OPTION;
 }, [selectedCourseId, courseOptionMap]);

🤖 Prompt for AI Agents

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

In `@src/features/course/filter-course/lib/useCourseFilter.ts` around lines 41 -
47, The current reverse-lookup in selectedCourseLabel iterates
courseOptionMap.entries() to find a label by selectedCourseId; instead maintain
an O(1) reverse map (e.g., courseLabelById) or keep a bidirectional structure so
selectedCourseLabel can directly lookup by id; update wherever courseOptionMap
is populated to also populate the reverse map and change the useMemo that
computes selectedCourseLabel (which references selectedCourseId and
courseOptionMap) to use the new reverse map for constant-time lookup and fall
back to ALL_COURSES_OPTION when null/missing.

src/shared/config/endpoints.ts (1)

10-15: ASSIGNMENTS.ROOT를 추가해 엔드포인트 단일 소스를 완성해 주세요.

현재 구조는 좋지만, src/entities/assignment/api/assignmentApi.ts Line [60]에서 여전히 '/assignments' 하드코딩이 필요해집니다. ROOT를 추가하면 일관성이 유지됩니다.

🗺️ 제안 수정안

   ASSIGNMENTS: {
+    ROOT: '/assignments',
     SCHEDULE: '/assignments/schedule',
     MY: '/assignments/my',
     DETAIL: (id: number | string) => `/assignments/${id}`,
     BY_COURSE: (courseId: number | string) => `/courses/${courseId}/assignments`,
   },

🤖 Prompt for AI Agents

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

In `@src/shared/config/endpoints.ts` around lines 10 - 15, Add a ROOT property to
the ASSIGNMENTS object (ASSIGNMENTS.ROOT = '/assignments') in the endpoints
definition so the base assignments path is a single source of truth, and then
replace any hardcoded '/assignments' usages (for example in assignmentApi where
the literal is used) with the shared constant (endpoints.ASSIGNMENTS.ROOT) to
keep endpoint references consistent.

src/features/course/filter-course/ui/CourseSelector.tsx (1)

3-11: Props 타입을 CourseSelectorProps로 분리해 주세요.

동작은 문제없지만, 현재 익명 객체 타입은 프로젝트 규칙과 불일치합니다. 명시적 Props 타입으로 분리하면 재사용/추론도 좋아집니다.

🧩 제안 수정안

+interface CourseSelectorProps {
+  options: string[];
+  value: string;
+  onSelect: (value: string) => void;
+}
+
 export const CourseSelector = ({
   options,
   value,
   onSelect,
-}: {
-  options: string[];
-  value: string;
-  onSelect: (value: string) => void;
-}) => {
+}: CourseSelectorProps) => {

As per coding guidelines "Props 타입: 컴포넌트명Props".

🤖 Prompt for AI Agents

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

In `@src/features/course/filter-course/ui/CourseSelector.tsx` around lines 3 - 11,
Create an explicit Props type named CourseSelectorProps and replace the
anonymous inline type in the CourseSelector declaration: define
CourseSelectorProps with options: string[]; value: string; onSelect: (value:
string) => void; then update the CourseSelector signature to accept props:
CourseSelectorProps (e.g., export const CourseSelector = ({ options, value,
onSelect }: CourseSelectorProps) => { ... }). Ensure the new type name is
exported if the component is used elsewhere.

src/features/auth/kakao/model/useKakaoLogin.ts (1)

14-23: 라우팅 상수 사용을 성공/에러 분기까지 완전히 맞춰주세요.

같은 훅 내에서 문자열 경로와 ROUTES가 섞여 있어 유지보수 시 추적 비용이 늘어납니다. 한 번에 통일하는 편이 안전합니다.
참고 문서: https://reactrouter.com/api/hooks/useNavigate

리팩터 예시

     onSuccess: ({response}) => {
       const userType = response.role === 'ADMIN' ? 'admin' : 'student';
       login(response.name, userType, response.accessToken);
-      navigate(userType === 'admin' ? '/admin' : '/student');
+      navigate(
+        userType === 'admin' ? ROUTES.ADMIN.ROOT : ROUTES.STUDENT.ROOT
+      );
     },
     onError: (error) => {
       console.error('Login error:', error);
       alert('로그인에 실패했습니다. 다시 시도해주세요.');
-      navigate('/');
+      navigate(ROUTES.ROOT);
     },

🤖 Prompt for AI Agents

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

In `@src/features/auth/kakao/model/useKakaoLogin.ts` around lines 14 - 23, The
onSuccess/onError handlers in useKakaoLogin mix hardcoded string routes with the
ROUTES constant; change navigate('/admin'), navigate('/student') and
navigate('/') to use the ROUTES constants (e.g. ROUTES.ADMIN, ROUTES.STUDENT,
ROUTES.HOME) so routing is consistent across the hook, keep the existing
userType/login logic (response.role check and login(response.name, userType,
response.accessToken)), and add/import the ROUTES symbol at the top of the file
if it isn’t already imported.

src/entities/assignment/api/assignmentApi.ts (1)

54-70: 신규 API도 ENDPOINTS 상수로 통일해 주세요.

getAssignment, createAssignment, updateAssignment에 문자열 경로가 남아 있어 같은 파일 내 패턴이 깨집니다. 경로 변경 시 누락 리스크가 생깁니다.
참고 문서: https://axios-http.com/docs/instance

리팩터 예시

 export const getAssignment = async (assignmentId: number) => {
-  const response = await privateAxios.get(`/assignments/${assignmentId}`);
+  const response = await privateAxios.get(
+    ENDPOINTS.ASSIGNMENTS.DETAIL(assignmentId)
+  );
   return apiResponseSchema(assignmentDetailSchema).parse(response.data);
 };
 ...
 export const updateAssignment = async (
   assignmentId: number,
   form: TAssignmentForm
 ) => {
-  const response = await privateAxios.put(`/assignments/${assignmentId}`, form);
+  const response = await privateAxios.put(
+    ENDPOINTS.ASSIGNMENTS.DETAIL(assignmentId),
+    form
+  );
   return apiResponseSchema(assignmentDetailSchema).parse(response.data);
 };

createAssignment도 ENDPOINTS.ASSIGNMENTS에 생성용 루트 상수를 추가해 같은 방식으로 맞추는 것을 권장합니다.

🤖 Prompt for AI Agents

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

In `@src/entities/assignment/api/assignmentApi.ts` around lines 54 - 70, Replace
hard-coded route strings in getAssignment, createAssignment, and
updateAssignment with the shared ENDPOINTS constants to keep endpoints
consistent; use ENDPOINTS.ASSIGNMENTS for the collection POST (createAssignment)
and the collection GET/POST root, and construct the detail path for
getAssignment and updateAssignment by appending the assignmentId to the
appropriate ENDPOINTS constant (e.g.,
`${ENDPOINTS.ASSIGNMENTS}/${assignmentId}`) or introduce a new
ENDPOINTS.ASSIGNMENT_BY_ID pattern if your ENDPOINTS object prefers templated
keys; update the calls in getAssignment, createAssignment, updateAssignment to
use those ENDPOINTS symbols instead of string literals and add the new constant
to the ENDPOINTS definition if needed.

src/entities/course/model/schemas.ts (1)

13-13: description 기본값이 계약 오류까지 삼킵니다.

z.string().catch('')는 null/undefined 보정뿐 아니라 숫자·객체 같은 모든 검증 실패도 전부 빈 문자열로 바꿉니다. 같은 description이 dashboardCourseSchema(25행)에서는 여전히 strict이어서, 엔드포인트마다 파싱 기준이 갈려버립니다.

null | undefined만 빈 문자열로 기본화하고 다른 타입 오류는 실패시키려면 Zod 공식 문서의 nullish() + transform() 패턴을 사용하세요:

-  description: z.string().catch(''),
+  description: z.string().nullish().transform((v) => v ?? ''),

이렇게 하면 null | undefined만 ''로 변환되고, 실제 타입 불일치는 파싱 에러로 올바르게 캐치됩니다.

🤖 Prompt for AI Agents

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

In `@src/entities/course/model/schemas.ts` at line 13, The description field
currently uses z.string().catch('') which swallows all validation errors; change
the schema for description (the description property in the course schema(s),
e.g., where description is defined alongside dashboardCourseSchema) to only
coerce null/undefined to '' and still fail on wrong types by using the
nullish()+transform() pattern from Zod (e.g., apply
z.string().nullish().transform(v => v ?? '') so only null/undefined become an
empty string while other type mismatches continue to produce validation errors).

src/entities/course/model/courseSchema.ts (1)

16-26: 응답 래퍼 스키마는 공통 헬퍼로 통일하는 편이 안전합니다.

현재 success/response 래퍼를 여기서 직접 정의하고 있는데, src/entities/course/api/courseApi.ts Line 15, Line 23, Line 29는 apiResponseSchema(...)를 사용합니다. 응답 래퍼가 이원화되면 추후 필드 변경 시 한쪽만 수정되는 드리프트가 생기기 쉽습니다. 공통 래퍼 헬퍼를 재사용해 한 곳에서 관리하는 쪽을 권장합니다.
참고: Zod object composition docs — https://zod.dev

🤖 Prompt for AI Agents

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

In `@src/entities/course/model/courseSchema.ts` around lines 16 - 26, The response
wrapper is defined inline in createCourseResponseSchema causing duplication with
apiResponseSchema used in courseApi.ts; replace the inline wrapper by composing
the course payload with the shared helper apiResponseSchema — define a
coursePayload schema (fields id, title, section, year, semester:
semesterCodeSchema, description) and createCourseResponseSchema by calling
apiResponseSchema(coursePayload) so the wrapper is centralized and future
changes only need to be made in the shared helper.

src/shared/ui/LabeledInput.tsx (1)

19-19: required 기본값이 true입니다 — 의도된 설계인지 확인해주세요.

일반적으로 HTML input의 required 기본값은 false입니다. 프로젝트의 모든 입력 필드가 기본적으로 필수라면 괜찮지만, 그렇지 않다면 예상치 못한 유효성 검사 동작이 발생할 수 있습니다.

🔧 기본값 변경 제안 (필요한 경우)

-      required = true,
+      required = false,

🤖 Prompt for AI Agents

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

In `@src/shared/ui/LabeledInput.tsx` at line 19, The prop default for required in
the LabeledInput component is set to true which deviates from HTML's default and
may cause unexpected validation; change the default to false (or explicitly
document/confirm the intentional behavior) by updating the LabeledInput
props/default parameter (the required prop) so it defaults to false instead of
true, and adjust any callers/tests that rely on the current default to
explicitly pass required when needed.

Fix all unresolved CodeRabbit comments on this PR:

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

src/entities/assignment/api/assignmentQueries.ts (1)

4-4: getAssignment 이름 충돌은 별칭으로 분리하면 더 읽기 좋아집니다.

Line 4 import와 Line 39 프로퍼티 이름이 같아서, Line 42에서 참조 대상을 한 번 더 추적하게 됩니다. 작은 변경으로 가독성을 높일 수 있어요.

🔧 제안 코드

 import {
   getAllAssignments,
-  getAssignment,
+  getAssignment as fetchAssignment,
   getAssignmentsByCourse,
   getAssignmentSchedules,
 } from '@/entities/assignment/api/assignmentApi';
@@
   getAssignment: (assignmentId: number) =>
     queryOptions({
       queryKey: ['assignments', assignmentId],
-      queryFn: () => getAssignment(assignmentId),
+      queryFn: () => fetchAssignment(assignmentId),
       select: (data) => data.response,
     }),

Also applies to: 39-43

🤖 Prompt for AI Agents

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

In `@src/entities/assignment/api/assignmentQueries.ts` at line 4, The imported
symbol getAssignment conflicts with the local/exported property named
getAssignment, making references ambiguous; fix by aliasing the import (e.g.,
import { getAssignment as fetchAssignment } or as getAssignmentApi) and update
the export/object property to use that alias (or alternatively rename the
exported property and all local references) so references to getAssignment in
this module are unambiguous; ensure you update every use of the original
identifier in this file (places that call getAssignment, the export object
around the current property at/near the existing getAssignment entry, and any
internal callers) to the chosen alias.

src/entities/assignment/api/assignmentMutations.ts (1)

17-23: 업데이트 변수 객체 타입을 interface로 분리해 주세요.

Line 20-23의 인라인 객체 타입은 재사용성과 가독성 면에서 개선의 여지가 있습니다. 프로젝트 컨벤션에서 객체 타입은 interface로 정의하도록 안내하고 있으므로, UpdateAssignmentVariables 인터페이스로 추출하면 의도가 더 명확해질 겁니다.

참고: TypeScript Handbook - Interfaces
https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#interfaces

🔧 제안 코드

 import type {TAssignmentForm} from '@/entities/assignment/model/schemas';
 import {createAssignment,updateAssignment,deleteAssignment} from '@/entities/assignment/api/assignmentApi';

+interface UpdateAssignmentVariables {
+  assignmentId: number;
+  form: TAssignmentForm;
+}
+
 export const assignmentMutations = {
   updateAssignment: {
     mutationKey: ['updateAssignment'],
-    mutationFn: ({
-      assignmentId,
-      form,
-    }: {
-      assignmentId: number;
-      form: TAssignmentForm;
-    }) => updateAssignment(assignmentId, form),
+    mutationFn: ({assignmentId, form}: UpdateAssignmentVariables) =>
+      updateAssignment(assignmentId, form),
   },
 };

🤖 Prompt for AI Agents

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

In `@src/entities/assignment/api/assignmentMutations.ts` around lines 17 - 23,
Extract the inline parameter type used in mutationFn into a named interface
UpdateAssignmentVariables and use it in the mutationFn signature; specifically,
create interface UpdateAssignmentVariables { assignmentId: number; form:
TAssignmentForm } (adjacent to or above mutationFn) and replace the inline type
for the parameters of mutationFn with UpdateAssignmentVariables so the call to
updateAssignment(assignmentId, form) keeps the same semantics but the variables
type is reusable and clearer.

src/entities/assignment/api/assignmentApi.ts (1)

56-78: 엔드포인트 상수화 제안

코드에서 getAssignment와 updateAssignment는 ENDPOINTS.ASSIGNMENTS.DETAIL()를 활용하는 것이 좋습니다. 이렇게 하면 파일 내 일관성이 유지되고, 엔드포인트 변경 시 한곳에서만 수정할 수 있어 유지보수성이 향상됩니다.

다만 createAssignment의 /assignments 엔드포인트는 현재 ENDPOINTS 상수에 정의되어 있지 않습니다. 다음 두 가지 방안을 제안합니다:

1. 권장: @/shared/config/endpoints에 ENDPOINTS.ASSIGNMENTS.ROOT 또는 BASE 상수를 추가 후 사용
2. 현재 상태 유지: 기본 경로는 하드코딩하되, 상세 조회/수정은 상수화

♻️ 일관성을 위한 리팩토링 예시

 // 과제 조회 API
 export const getAssignment = async (assignmentId: number) => {
-  const response = await privateAxios.get(`/assignments/${assignmentId}`);
+  const response = await privateAxios.get(ENDPOINTS.ASSIGNMENTS.DETAIL(assignmentId));
   const parsed = apiResponseSchema(assignmentDetailSchema).parse(response.data);
   return parsed.response;
 };

 // 과제 추가 API
 export const createAssignment = async (form: TAssignmentForm) => {
-  const response = await privateAxios.post('/assignments', form);
+  const response = await privateAxios.post(ENDPOINTS.ASSIGNMENTS.ROOT, form);
   const parsed = apiResponseSchema(assignmentDetailSchema).parse(response.data);
   return parsed.response;
 };

 // 과제 수정 API
 export const updateAssignment = async (
   assignmentId: number,
   form: TAssignmentForm
 ) => {
-  const response = await privateAxios.put(`/assignments/${assignmentId}`, form);
+  const response = await privateAxios.put(ENDPOINTS.ASSIGNMENTS.DETAIL(assignmentId), form);
   const parsed = apiResponseSchema(assignmentDetailSchema).parse(response.data);
   return parsed.response;
 };

🤖 Prompt for AI Agents

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

In `@src/entities/assignment/api/assignmentApi.ts` around lines 56 - 78, Replace
hardcoded assignment URLs with the centralized endpoint constants: change
getAssignment and updateAssignment to use
ENDPOINTS.ASSIGNMENTS.DETAIL(assignmentId) and replace the '/assignments'
literal in createAssignment with a new ENDPOINTS.ASSIGNMENTS.ROOT (or BASE)
constant; add ENDPOINTS.ASSIGNMENTS.ROOT to the endpoints module (e.g.,
'@/shared/config/endpoints') and update createAssignment to post to that
constant to keep all assignment routes consistent and maintainable.

src/features/course/filter-course/lib/useCourseFilter.ts (1)

33-41: handleCourseSelect에 useCallback 적용을 권장합니다.

현재 handleCourseSelect는 일반 함수로 선언되어 있어 매 렌더링마다 새로운 함수 참조가 생성됩니다. AssignmentManagePage 등에서 이 함수를 자식 컴포넌트에 prop으로 전달할 경우, 불필요한 리렌더링이 발생할 수 있습니다.

♻️ useCallback 적용 제안

+import {useCallback, useMemo, useState} from 'react';
-import {useMemo, useState} from 'react';

-  const handleCourseSelect = (value: string) => {
+  const handleCourseSelect = useCallback((value: string) => {
     if (value === ALL_COURSES_OPTION) {
       setSelectedCourseId(null);
       return;
     }

     const courseId = courseMaps.labelToId.get(value) ?? null;
     setSelectedCourseId(courseId);
-  };
+  }, [courseMaps.labelToId]);

📚 참고: React useCallback 공식 문서

🤖 Prompt for AI Agents

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

In `@src/features/course/filter-course/lib/useCourseFilter.ts` around lines 33 -
41, The handler handleCourseSelect is recreated on every render which can cause
unnecessary re-renders when passed to children; wrap it with React.useCallback
and memoize it by including its dependencies [setSelectedCourseId,
courseMaps.labelToId] (and ALL_COURSES_OPTION if not a constant) so the function
identity is stable; update the declaration of handleCourseSelect to use
useCallback(...) and keep the same internal logic (check ALL_COURSES_OPTION,
lookup courseMaps.labelToId, call setSelectedCourseId).

src/shared/ui/ConfirmModal.tsx (1)

21-23: Dismiss 제어 옵션을 추가해 비동기 진행 중 닫힘을 막는 편이 안전합니다.
Escape/backdrop이 항상 onCancel을 호출해서, 삭제처럼 진행 중인 작업에서 모달이 먼저 닫힐 수 있습니다. isDismissible(기본 true) 같은 prop으로 Escape/backdrop/취소 버튼 동작을 일괄 제어해 주세요.
참고: WAI-ARIA Modal Dialog 패턴 — https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/

🔧 제안 수정안

 interface ConfirmModalProps {
   title: string;
   description?: string;
   confirmLabel?: string;
   cancelLabel?: string;
   onConfirm: () => void;
   onCancel: () => void;
+  isDismissible?: boolean;
 }

 export default function ConfirmModal({
   title,
   description,
   confirmLabel = '확인',
   cancelLabel = '취소',
   onConfirm,
   onCancel,
+  isDismissible = true,
 }: ConfirmModalProps) {
   useEffect(() => {
     const handleEsc = (e: KeyboardEvent) => {
-      if (e.key === 'Escape') onCancel();
+      if (e.key === 'Escape' && isDismissible) onCancel();
     };
     window.addEventListener('keydown', handleEsc);
     return () => window.removeEventListener('keydown', handleEsc);
-  }, [onCancel]);
+  }, [onCancel, isDismissible]);

   return (
     <div
       className='fixed inset-0 z-50 flex items-center justify-center bg-black/40'
-      onClick={onCancel}>
+      onClick={isDismissible ? onCancel : undefined}>
       <section
         role='dialog'
         aria-modal='true'
         aria-labelledby='confirm-modal-title'
         className='bg-white rounded-2xl p-8 w-80 flex flex-col gap-6 shadow-lg'
         onClick={(e) => e.stopPropagation()}>
@@
-          <Button color='secondary' onClick={onCancel}>
+          <Button color='secondary' onClick={() => isDismissible && onCancel()}>
             {cancelLabel}
           </Button>

Also applies to: 32-32

🤖 Prompt for AI Agents

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

In `@src/shared/ui/ConfirmModal.tsx` around lines 21 - 23, The ConfirmModal should
add an isDismissible prop (default true) and make all dismissal paths respect
it: update the Escape handler in the useEffect (handleEsc), the backdrop/click
handler, and the cancel button click handler inside ConfirmModal to no-op when
isDismissible is false so ongoing async actions cannot close the modal; ensure
prop is optional with default true and document that it controls
Escape/backdrop/cancel dismissal behavior.

src/entities/course/model/schemas.ts (1)

16-19: description 필드 중복 정의 검토 필요

courseBaseSchema는 courseCoreSchema.extend()를 사용하므로, 이미 courseCoreSchema의 description 변환 로직을 상속받습니다. Line 18의 재정의는 동일한 변환 로직이라 불필요할 수 있습니다.

의도적으로 명시성을 위해 남겨둔 것이라면 주석으로 명확히 해주시고, 그렇지 않다면 제거를 고려해주세요.

♻️ 중복 제거 제안

 /** 강의 기본 정보 (ID 포함) */
 export const courseBaseSchema = courseCoreSchema.extend({
   id: z.number(),
-  description: z.string().nullish().transform((v) => v ?? ''), // 응답에서는 기본값 처리
 });

🤖 Prompt for AI Agents

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

In `@src/entities/course/model/schemas.ts` around lines 16 - 19, courseBaseSchema
currently redefines the description transform that's already provided by
courseCoreSchema.extend(), creating a redundant duplicate; either remove the
description entry from the object passed to courseCoreSchema.extend() so
courseBaseSchema simply inherits the transform, or if the redefinition is
intentional for explicitness, leave it but add a clear comment above the
description line explaining why it must be redefined; target the
courseBaseSchema declaration and the description property inside it when making
the change.

Fix all unresolved CodeRabbit comments on this PR:

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