-
Notifications
You must be signed in to change notification settings - Fork 1
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
[FEAT] 시야찾기 2차 MVP V1 #106
Conversation
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.
관희 정말 너무 고생많았어!!!
고생의 흔적의 파일 62개나 바뀐것에서 느껴진다..
* (익사이팅석, 프리미엄석은 따로 구분) | ||
* @author : 조관희 | ||
*/ | ||
fun ResponseBlockReview.ResponseLocation.stadiumBlock(): String { |
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.
기존에 도메인에서 관리 하던것을 util로 다뺐구나!
뺀 이유가 궁금하네 이제 더이상 변할 수 없을 확률이 커서 UI 관련 표현 해주는(?) 로직이라서 util로 관리를 하는건가?
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.
코드가 너무 길어져서 별도 파일로 빼는게 좋아보여서 뺐어!
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.
아하 그렇구만 다른 의도가 있는줄 알았어 나도 리뷰 부분이 점점 비대해지는데 고려해봐야겠다👍
page = 0, | ||
size = 10 | ||
cursor = null, | ||
sortBy = "DATE_TIME", |
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.
아직 시간순 밖에 없지만 추후 공감순도 있을수 있으니 enum으로 처리해놔도 괜찮을듯 싶은데!
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.
엉 Enum 으로 빼서 해도 좋을 것 같아!
class SingleLiveEvent<T> : MutableLiveData<T?>() { | ||
private val mPending = AtomicBoolean(false) |
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.
져번에 성식이가 말했던 방식으로 해결한거구나!👍👍👍
@@ -0,0 +1,6 @@ | |||
<?xml version="1.0" encoding="utf-8"?> | |||
<shape xmlns:android="http://schemas.android.com/apk/res/android" |
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.
지금 drawable 쓱 보고 왔는데 이것도 rect_transparent_black03 / rect_transparentblack03 이런식으로 각각 쓰는 방식이 다른것 같네..🤣
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.
나중에 중복되는건 수정해서 하나로 통일하면 좋을듯
가시성으로는 왼쪽게 좋아보이는데 _ 구분자가 들어가서 하나의 색상이라 보기도 애매해서 그런 점에서는 오른쪽 네이밍이 좋아보이고..
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.
통일 좋아 ,, 그리고 지금 같은 컬러인데 기존 디자인 시스템이 정의되지 않았을 때 (grayscales100, white --- )와 정의된 네이밍 (backgroundTertiary, actionEnabled ---) 도 겹치는게 많은 것 같아서 나중에 싹 정리해보쟈 !
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.
고생했어 ~~ 😎😎 복잡한 뷰인데 뚝딱 해내시네욥 최고 ~~~ 👍
val blockFilters = _blockFilters | ||
|
||
private val _sections = SingleLiveEvent<List<Section>>() | ||
val sections = _sections |
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.
StadiumActivity 뷰모델 변수들을 다 SingleLiveEvent로 처리한 이유가 UI 상태 변화 결과가 한번만 전달되도록 하기 위해서 맞남 ?!
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.
내가 사용한 의도는 LiveData 중복호출 문제로 SingleLiveEvent 를 사용했어!
in listOf("exciting3") -> "$stadiumName 3루 $sectionName" | ||
in listOf("premium") -> "$stadiumName $sectionName" | ||
else -> "$stadiumName $base $sectionName" | ||
} |
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.
추후에 야구장이 추가될 때 이렇게 코드가 추가되는 상황이 생길 수도 있을 것 같은데 나중에 서버와 다시 논의해보는게 좋을 것 같다는 생각이 들어 ...! 🤔🤔
@@ -0,0 +1,6 @@ | |||
<?xml version="1.0" encoding="utf-8"?> | |||
<shape xmlns:android="http://schemas.android.com/apk/res/android" |
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.
통일 좋아 ,, 그리고 지금 같은 컬러인데 기존 디자인 시스템이 정의되지 않았을 때 (grayscales100, white --- )와 정의된 네이밍 (backgroundTertiary, actionEnabled ---) 도 겹치는게 많은 것 같아서 나중에 싹 정리해보쟈 !
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.
조창정 폼 미쳤다~~~~~! 고생했엉
@Composable | ||
fun MultiStyleText(style: TextStyle, vararg textWithColors: Pair<String, Color>) { | ||
Text( | ||
buildAnnotatedString { | ||
textWithColors.forEach { (text, color) -> | ||
withStyle(style = SpanStyle(color = color)) { | ||
append(text) | ||
} | ||
} | ||
}, | ||
style = style | ||
) | ||
} |
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.
잘쓰겠습니당~
💻주요 작업 내용
🎞리뷰 요청 사항
시연영상
2024-08-21.11.mp4
컴포저블 컴포넌트 UI