-
Couldn't load subscription status.
- Fork 0
feat: creators 페이지 input 내용으로 조회 #60
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
Open
plagdoctor
wants to merge
1
commit into
develop
Choose a base branch
from
feature/creators-input
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
저희 현재 UI 플로우 상, 강의 페이지(
/lectures)와 크리에이터 페이지(/creators)에서 Input 클릭 시에는 검색 페이지로 redirect 하도록 되어있습니다 !해당 페이지에서는 Input 컴포넌트의 value를 핸들링하는
handleChange와 검색 버튼을 눌렀을 때 핸들링하는handleSearchButton는 제거되고, Input 컴포넌트 클릭시에router.push('/search')만 해줘도 될 것 같습니당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.
아 저는 검색 결과 나온 상태에선 라우팅 되는 거보다 페이지 내에서 검색 정보 입력되는 게 나아 보였는데요. 모바일 네이버 보니까 또 말씀 하신 게 맞는 거 같고요.. + 로 키워드 제안 되는 것도 생각하면 이동하는 게 맞아 보이네요. 말씀 주신 거에 맞춰서 변경하겠습니다. 👍