-
Notifications
You must be signed in to change notification settings - Fork 0
[FE-224] fix: 마이페이지 검색 QA 버그 픽스 #229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for record-it-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Seongtaek-H
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
확인했습니다.
마이레코드에서 처음에 검색 결과 페이지로 이동하려면 무조건 엔터키를 눌러야하네요? 저는 change 이벤트 발생하면 디바운스 적용 후 바로 이동하는 것으로 생각했는데 정책서랑 TC를 봐도 좀 애매하긴하네요.
endmoseung
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
확인했습니다!
| setIsClickedInput, | ||
| ...props | ||
| }: SearchInputProps) { | ||
| const KEYWORD_MAX_LENGTH = 12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
저희 이 12는 모두가 하나의 상수로 두고 써야될것같아요
예를들어 우리가 12> 15로 정책이 바뀌면 레코드 추가페이지에서도 수정해야하고, 워터페이지에도 수정해야하니 하나의 상수만 변경해도 모두가 반영되도록하는게 유지보수에 유리할거같아요!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
넵넵 :) 반영해놓을게요!
오늘 QA 때 얘기해보고 변경된다면 배포 전에 반영해보도록 하겠습니다 :) |
작업 내용
참고 이미지(선택)
어떤 점을 리뷰 받고 싶으신가요?