Conversation
WalkthroughModal 컴포넌트가 내부 컨텐츠 컨테이너의 스타일링을 위해 새로운 선택적 prop Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Update: 2026년 02월 03일 18시 08분 14초 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@src/shared/ui/Modal/Modal.tsx`:
- Line 65: The className prop in the Modal component is calling the cn() utility
with a single static string (className={cn('fixed inset-0 z-50 flex w-full
items-center justify-center')}), which is unnecessary; change it to use the
string directly (className='fixed inset-0 z-50 flex w-full items-center
justify-center') and remove any now-unused import of cn to keep the Modal
component and its imports clean.
- Line 67: The backdrop div in Modal (Modal.tsx) is currently clickable but not
keyboard-accessible; update the element that uses handleOutsideClick to be
keyboard-interactive by adding role="button", tabIndex={0}, an accessible label
(aria-label="Close modal" or similar), and an onKeyDown handler that calls
handleOutsideClick when the user presses Enter, Space, or Escape; ensure the
handler signature matches handleOutsideClick usage so it can accept the
synthetic/event parameter from both onClick and onKeyDown.
keemsebin
left a comment
There was a problem hiding this comment.
변경을 진행했을 때 기존 Modal의 className을 사용하는 코드들은 문제가 생길 것 같습니다. 기존 className을 지우지 않고, 내부에서 사용하는 contentClassName을 별도 props로 지정해줘야 할 것 같아요.
099ea14 수정하였습니다! |
|
고생하셨습니다! |
🔥 연관 이슈
🚀 작업 내용
🤔 고민했던 내용
💬 리뷰 중점사항
Summary by CodeRabbit
릴리스 노트