-
Notifications
You must be signed in to change notification settings - Fork 1
SCRUM-254 design: search input component #24
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
SCRUM-254 design: search input component #24
Conversation
hyunjung-choi
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.
수고하셨습니다 !! 👍👍👍
몇 가지 수정 사항 제안했는데, 확인 부탁드려용
app/src/main/java/com/lyrics/feelin/core/designsystem/component/FeelinSearchInputField.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/com/lyrics/feelin/core/designsystem/component/FeelinSearchInputField.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/com/lyrics/feelin/core/designsystem/component/FeelinSearchInputField.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/com/lyrics/feelin/core/designsystem/component/FeelinSearchInputField.kt
Show resolved
Hide resolved
- make InputClearButton component - use icon instead image to render vector img - add onSearchClick parameter - add options for search field - lineLimits - keyboardOptions(imeAction, keyboard type) - onKeyboardAction - maxLength
|
말씀주신 사항들 수정했습니다! 한번 다시 확인 부탁드려요 |
hyunjung-choi
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.
주말인데 고생하셨습니다 ! 👍
- remove unnecessary InputClearButton
- FeelinSearchInputField - InnerTextFieldComponent
|
확인해주셔서 감사합니다! 새로 컴포넌트로 묶은 부분도 큰 문제 없으면 머지하겠습니다. |
|
오 ! 좋아요 !! 바로 머지합시당 |
감사합니다! |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
What is the current behavior?
SCRUM-254
곡 추가, 아티스트 검색 등에서 사용하는 검색창 컴포넌트가 없는 상황입니다.
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking changes.
ScreenShots (If needed)
Other information: