Feature/#43 #75

Hongji03 · 2026-01-28T09:36:53Z

📝 설명

해당 PR이 진행한 사항을 자세히 적어주세요.
Home 부분의 QA를 일부 진행하였습니다.

✔️ PR 유형

어떤 변경 사항이 있나요?

📎 관련 이슈 번호

해당 PR과 관련된 이슈 번호를 적어주세요.

#43

Summary by CodeRabbit

릴리스 노트

새로운 기능
- 감정 및 작업 선택 시 요약 행 표시 기능 추가
- UI 요소에 확장/축소 애니메이션 효과 추가
- 새로운 배경 그래디언트 색상 테마 추가
디자인
- 감정 선택 아이콘에 회색 톤 옵션 추가
- 배경 및 선택 상태 스타일링 개선
- 전체 UI 테마 일관성 강화

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-28T09:37:10Z

워크스루

테마 색상 시스템에 새로운 backgroundmaincolor 속성을 추가하고, HomeScreen의 상태 관리와 UI 레이아웃을 리팩토링하여 추천 표시 로직과 상단 바 축소 동작을 개선했습니다. 또한 여러 이모션 관련 UI 컴포넌트를 업데이트하고 회색조 아이콘 리소스를 추가했습니다.

변경 사항

코호트 / 파일(s)	변경 요약
테마 색상 속성 추가 `design/src/main/java/com/example/design/theme/color/Basic.kt`, `design/src/main/java/com/example/design/theme/color/ThemeColorScheme.kt`	두 파일에 새로운 공개 속성 `backgroundmaincolor: Brush`를 추가했습니다. Basic.kt에서는 수평 그래디언트로 초기화되고, ThemeColorScheme.kt에서는 sealed 클래스의 프로퍼티로 선언됩니다.
HomeScreen 상태 관리 및 UI 리팩토링 `feature/home/src/main/java/com/example/home/screen/HomeScreen.kt`	상단 바 축소 로직을 `collapsedByScroll`과 `topBarCollapsed` 상태로 변경했습니다. `showRecs` 상태와 `hasRequestedRecommend` 플래그를 추가하여 추천 표시/숨김 제어를 개선했습니다. 동적 바닥글 높이 계산 로직을 추가하고 기존 UI 컴포넌트들을 리팩토링했습니다.
상단 바 및 컴포넌트 업데이트 `feature/home/src/main/java/com/example/home/ui/top/bar/HomeTopBar.kt`, `feature/home/src/main/java/com/example/home/ui/top/bar/component/EmotionSelector.kt`, `feature/home/src/main/java/com/example/home/ui/top/bar/component/TaskSelector.kt`	HomeTopBar에 `isCollapsed`, `onExpandClick`, `hasRequestedRecommend` 파라미터를 추가하고 애니메이션 가시성 제어를 적용했습니다. EmotionSelector와 TaskSelector의 배경색 로직을 조건부 Modifier.background로 리팩토링했습니다.
선택 요약 행 컴포넌트 `feature/home/src/main/java/com/example/home/ui/top/bar/component/SelectedSummaryRow.kt`	새로운 공개 Composable 함수 `SelectedSummaryRow`를 추가했습니다. 선택된 이모션 ID와 작업 ID를 해당 아이콘 및 레이블로 매핑하여 보여줍니다. 유효하지 않은 ID에 대해 런타임 검증을 포함합니다.
회색조 아이콘 리소스 `feature/home/src/main/res/drawable/ic_*_gray.xml`	기존 이모션 아이콘들(`ic_anger_gray.xml`, `ic_calm_gray.xml`, `ic_excite_gray.xml`, `ic_joy_gray.xml`, `ic_sad_gray.xml`)에서 strokeAlpha/fillAlpha 속성을 제거하고 fillColor를 회색조 톤으로 업데이트했습니다. 새로운 `ic_irritation_gray.xml` 파일을 추가했습니다.

예상 코드 리뷰 노력

🎯 4 (복잡함) | ⏱️ ~45분

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	PR 제목이 너무 모호하고 구체적인 정보를 제공하지 않습니다. 'Feature/#43'은 이슈 번호만 나타낼 뿐 실제 변경 사항을 명확히 설명하지 못합니다.	PR 제목을 더 구체적으로 변경하세요. 예: 'Add background main color and fix Home TopBar collapse behavior' 또는 'Update Home screen UI with gradient backgrounds and fix TopBar collapse'

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

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.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 5

🤖 Fix all issues with AI agents

In `@feature/home/src/main/java/com/example/home/screen/HomeScreen.kt`:
- Around line 228-241: The click handler onRecommendClick sets
hasRequestedRecommend = true too early (before validating
selectedEmotion/selectedTask), causing the UI to show "requested" even when no
request is made; change it so hasRequestedRecommend is only assigned true inside
the conditional where selectedEmotion != null && selectedTask != null (i.e.,
after onClearNeedMoreNotice() and immediately before or after
onRecommendRequest(selectedEmotion!!, selectedTask!!, 10)), and remove the
initial pre-check assignment so no flag is set when inputs are missing.

In
`@feature/home/src/main/java/com/example/home/ui/top/bar/component/SelectedSummaryRow.kt`:
- Around line 50-58: The current code uses require checks that will throw on
invalid IDs (in selectedEmotionIcon and selectedTaskLabel); change these to
defensive lookups and return sensible fallbacks instead of crashing: for
selectedEmotionIcon, replace the require/idx logic with a safe lookup (use
emotionIds.indexOf(selectedEmotionId) followed by colorIcons.getOrNull(idx) or a
default icon when null) and for selectedTaskLabel, avoid requireNotNull and use
situations.firstOrNull { it.id == selectedTaskId }?.name ?: fallbackLabel or
null so the caller/UI can skip rendering or show a placeholder; update any UI
that consumes selectedEmotionIcon/selectedTaskLabel to handle null/default
values.

In `@feature/home/src/main/java/com/example/home/ui/top/bar/HomeTopBar.kt`:
- Around line 231-238: The Image in HomeTopBar.kt currently sets
contentDescription = null making the clickable expand icon inaccessible; update
the Image composable to provide a descriptive contentDescription using
stringResource (e.g., stringResource(R.string.expand_section) or a suitable
existing string) and pass that instead of null, ensuring the description
references the onExpandClick action so screen readers announce the purpose; if
no string exists, add a new string resource like "Expand" and use
stringResource(...) for the contentDescription.

In `@feature/home/src/main/res/drawable/ic_anger_gray.xml`:
- Around line 24-29: Remove the duplicated circle path elements that repeat the
same android:pathData and android:fillColor; specifically find the path elements
with android:pathData="M33,25C33,26.105 31.657,27 30,27C28.343,27 27,26.105
27,25C27,23.895 28.343,23 30,23C31.657,23 33,23.895 33,25Z" and
android:pathData="M17,25C17,26.105 15.657,27 14,27C12.343,27 11,26.105
11,25C11,23.895 12.343,23 14,23C15.657,23 17,23.895 17,25Z" where they appear
twice, and delete the second occurrences (the duplicates) while keeping a single
instance of each path with android:fillColor="#CFCFCF".

In `@feature/home/src/main/res/drawable/ic_irritation_gray.xml`:
- Around line 18-22: gradient 요소 내에 같은 android:offset="0"이 두 번 사용되어 중복된 스탑이
무시됩니다; gradient 태그(gradient)를 찾아 item 요소들(현재 두 개의 android:offset="0"을 가진 item)을
수정하여 의도된 그라데이션이 나오도록 하나의 offset을 변경(예: 첫째를 0, 둘째를 0.5 등으로 조정)하거나 중복된 색상 stop이
불필요하면 해당 item을 삭제하여 중복을 제거하세요.

🧹 Nitpick comments (4)

design/src/main/java/com/example/design/theme/color/ThemeColorScheme.kt (1)

9-10: 네이밍 컨벤션 일관성 검토

backgroundmaincolor가 기존 maincolor와 동일한 소문자 패턴을 따르고 있습니다. Kotlin 표준 camelCase 컨벤션(backgroundMainColor)과는 다르지만, 코드베이스 내 기존 패턴과 일관성이 있으므로 현재 상태로 유지해도 무방합니다.
feature/home/src/main/java/com/example/home/ui/top/bar/component/SelectedSummaryRow.kt (1)
67-76: 모서리 shape 불일치 정리 권장

clip(10dp) vs background(18dp) vs border(10dp)가 불일치라 모서리 품질이 들쭉날쭉해질 수 있습니다. 동일 shape 상수로 통일하는 편이 안전합니다.
♻️ 제안 수정
+    val chipShape = RoundedCornerShape(10.dp)
+
     Row(
         modifier = Modifier.fillMaxWidth(),
         verticalAlignment = Alignment.CenterVertically
     ) {
@@
         Box(
             modifier = Modifier
                 .size(32.dp)
-                .clip(RoundedCornerShape(10.dp))
-                .background(brush = LocalColorTheme.current.backgroundmaincolor, shape = RoundedCornerShape(18.dp))
+                .clip(chipShape)
+                .background(brush = LocalColorTheme.current.backgroundmaincolor, shape = chipShape)
                 .border(
                     width = 1.dp,
                     brush = Basic.maincolor,
-                    shape = RoundedCornerShape(10.dp)
+                    shape = chipShape
                 ),
             contentAlignment = Alignment.Center
         ) {
feature/home/src/main/java/com/example/home/screen/HomeScreen.kt (2)

139-193: 주석 처리된 이전 구현은 제거를 권장합니다.

대량의 주석 블록이 남아 있으면 유지보수/리뷰 시 혼동을 줍니다. 필요 없다면 삭제하고, 참고 목적이라면 문서나 ADR로 옮겨 주세요.

244-273: footerHeight의 800.dp 하드코딩은 화면별 여백 과다 위험이 있습니다.

소형 기기에서 800.dp가 화면보다 커 불필요한 빈 스크롤이 생길 수 있습니다. screenHeight 비율 기반으로 상/하한을 두는 방식으로 조정 검토해 주세요.

coderabbitai · 2026-01-28T09:43:37Z

feature/home/src/main/java/com/example/home/screen/HomeScreen.kt

    val onRecommendClick: () -> Unit = {
+        hasRequestedRecommend = true // 클릭 기록
+        // 선택 없어도 접히는건 스크롤이 담당
+        // 추천 요청은 선택이 있어야만
        if (selectedEmotion != null && selectedTask != null) {
-            onClearNeedMoreNotice() // 이전 안내 끄기
+            onClearNeedMoreNotice()
            onRecommendRequest(selectedEmotion!!, selectedTask!!, 10)
            showRecs = true
+
+            // 추천 눌렀으면 강제 접힘(스크롤 상관 없이)
            isTopBarLockedCollapsed = true
-            isTopBarExpanded = false
+
            coroutineScope.launch { listState.animateScrollToItem(1) }
        }


⚠️ Potential issue | 🟡 Minor

선택 없이 클릭해도 hasRequestedRecommend가 true가 됩니다.

감정/상황 미선택 시에도 ‘요청됨’ 상태로 보일 수 있어 UX 혼란이 생길 수 있습니다. 실제 요청이 시작될 때만 플래그를 세팅하는 쪽이 안전합니다.

🔧 수정 제안

val onRecommendClick: () -> Unit = { - hasRequestedRecommend = true // 클릭 기록 // 선택 없어도 접히는건 스크롤이 담당 // 추천 요청은 선택이 있어야만 if (selectedEmotion != null && selectedTask != null) { + hasRequestedRecommend = true // 클릭 기록 onClearNeedMoreNotice() onRecommendRequest(selectedEmotion!!, selectedTask!!, 10) showRecs = true

🤖 Prompt for AI Agents

In `@feature/home/src/main/java/com/example/home/screen/HomeScreen.kt` around lines 228 - 241, The click handler onRecommendClick sets hasRequestedRecommend = true too early (before validating selectedEmotion/selectedTask), causing the UI to show "requested" even when no request is made; change it so hasRequestedRecommend is only assigned true inside the conditional where selectedEmotion != null && selectedTask != null (i.e., after onClearNeedMoreNotice() and immediately before or after onRecommendRequest(selectedEmotion!!, selectedTask!!, 10)), and remove the initial pre-check assignment so no flag is set when inputs are missing.

coderabbitai · 2026-01-28T09:43:37Z

feature/home/src/main/java/com/example/home/ui/top/bar/component/SelectedSummaryRow.kt

+    val selectedEmotionIcon = run {
+        val idx = emotionIds.indexOf(selectedEmotionId)
+        require(idx >= 0) { "Invalid selectedEmotionId: $selectedEmotionId" }
+        colorIcons[idx]
+    }
+
+    val selectedTaskLabel = requireNotNull(
+        situations.firstOrNull { it.id == selectedTaskId }?.name
+    ) { "Invalid selectedTaskId: $selectedTaskId (not found in situations)" }


⚠️ Potential issue | 🟠 Major

유효하지 않은 ID에서 런타임 크래시 가능

require로 바로 크래시가 발생할 수 있어 방어 로직이 필요합니다(예: 값 없으면 렌더링 스킵/대체 표시).

🐛 제안 수정

- val selectedEmotionIcon = run { - val idx = emotionIds.indexOf(selectedEmotionId) - require(idx >= 0) { "Invalid selectedEmotionId: $selectedEmotionId" } - colorIcons[idx] - } - - val selectedTaskLabel = requireNotNull( - situations.firstOrNull { it.id == selectedTaskId }?.name - ) { "Invalid selectedTaskId: $selectedTaskId (not found in situations)" } + if (selectedEmotionId == null || selectedTaskId == null) return + + val idx = emotionIds.indexOf(selectedEmotionId) + val selectedEmotionIcon = colorIcons.getOrNull(idx) ?: return + + val selectedTaskLabel = situations + .firstOrNull { it.id == selectedTaskId } + ?.name ?: return

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

val selectedEmotionIcon = run {

val idx = emotionIds.indexOf(selectedEmotionId)

require(idx >= 0) { "Invalid selectedEmotionId: $selectedEmotionId" }

colorIcons[idx]

}

val selectedTaskLabel = requireNotNull(

situations.firstOrNull { it.id == selectedTaskId }?.name

) { "Invalid selectedTaskId: $selectedTaskId (not found in situations)" }

if (selectedEmotionId == null || selectedTaskId == null) return

val idx = emotionIds.indexOf(selectedEmotionId)

val selectedEmotionIcon = colorIcons.getOrNull(idx) ?: return

val selectedTaskLabel = situations

.firstOrNull { it.id == selectedTaskId }

?.name ?: return

🤖 Prompt for AI Agents

In `@feature/home/src/main/java/com/example/home/ui/top/bar/component/SelectedSummaryRow.kt` around lines 50 - 58, The current code uses require checks that will throw on invalid IDs (in selectedEmotionIcon and selectedTaskLabel); change these to defensive lookups and return sensible fallbacks instead of crashing: for selectedEmotionIcon, replace the require/idx logic with a safe lookup (use emotionIds.indexOf(selectedEmotionId) followed by colorIcons.getOrNull(idx) or a default icon when null) and for selectedTaskLabel, avoid requireNotNull and use situations.firstOrNull { it.id == selectedTaskId }?.name ?: fallbackLabel or null so the caller/UI can skip rendering or show a placeholder; update any UI that consumes selectedEmotionIcon/selectedTaskLabel to handle null/default values.

coderabbitai · 2026-01-28T09:43:37Z

feature/home/src/main/java/com/example/home/ui/top/bar/HomeTopBar.kt

+                Image(
+                    painter = painterResource(R.drawable.ic_down_arrow),
+                    contentDescription = null,
+                    modifier = Modifier
+                        .width(44.dp)
+                        .align(Alignment.CenterHorizontally)
+                        .clickable { onExpandClick() }
                )


⚠️ Potential issue | 🟠 Major

접근성: 확장 버튼에 contentDescription 필요

클릭 가능한 아이콘에 contentDescription = null이면 스크린리더 사용자가 동작을 인지할 수 없습니다. 설명 텍스트를 추가하고, 가능하면 stringResource로 관리해 주세요.

🐛 제안 수정

Image( painter = painterResource(R.drawable.ic_down_arrow), - contentDescription = null, + contentDescription = "확장", modifier = Modifier .width(44.dp) .align(Alignment.CenterHorizontally) .clickable { onExpandClick() } )

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

Image(

painter = painterResource(R.drawable.ic_down_arrow),

contentDescription = null,

modifier = Modifier

.width(44.dp)

.align(Alignment.CenterHorizontally)

.clickable { onExpandClick() }

)

Image(

painter = painterResource(R.drawable.ic_down_arrow),

contentDescription = "확장",

modifier = Modifier

.width(44.dp)

.align(Alignment.CenterHorizontally)

.clickable { onExpandClick() }

)

🤖 Prompt for AI Agents

In `@feature/home/src/main/java/com/example/home/ui/top/bar/HomeTopBar.kt` around lines 231 - 238, The Image in HomeTopBar.kt currently sets contentDescription = null making the clickable expand icon inaccessible; update the Image composable to provide a descriptive contentDescription using stringResource (e.g., stringResource(R.string.expand_section) or a suitable existing string) and pass that instead of null, ensuring the description references the onExpandClick action so screen readers announce the purpose; if no string exists, add a new string resource like "Expand" and use stringResource(...) for the contentDescription.

coderabbitai · 2026-01-28T09:43:38Z

feature/home/src/main/res/drawable/ic_anger_gray.xml

  <path
      android:pathData="M33,25C33,26.105 31.657,27 30,27C28.343,27 27,26.105 27,25C27,23.895 28.343,23 30,23C31.657,23 33,23.895 33,25Z"
-      android:strokeAlpha="0.6"
-      android:fillColor="#FFC9BC"
-      android:fillAlpha="0.6"/>
+      android:fillColor="#CFCFCF"/>
  <path
      android:pathData="M17,25C17,26.105 15.657,27 14,27C12.343,27 11,26.105 11,25C11,23.895 12.343,23 14,23C15.657,23 17,23.895 17,25Z"
-      android:strokeAlpha="0.6"
-      android:fillColor="#FFC9BC"
-      android:fillAlpha="0.6"/>
+      android:fillColor="#CFCFCF"/>


⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

cat -n feature/home/src/main/res/drawable/ic_anger_gray.xml

Repository: LinkYou-2025/LinkU_Android

Length of output: 3949

🏁 Script executed:

# Search for the specific pathData in the file to see if it appears multiple times rg "M33,25C33,26.105" feature/home/src/main/res/drawable/ic_anger_gray.xml -n

Repository: LinkYou-2025/LinkU_Android

Length of output: 349

🏁 Script executed:

# Search for the left cheek pathData rg "M17,25C17,26.105" feature/home/src/main/res/drawable/ic_anger_gray.xml -n

Repository: LinkYou-2025/LinkU_Android

Length of output: 349

🏁 Script executed:

# Check other gray icon files for similar duplication patterns fd -e xml -path '*drawable*gray.xml' feature/home/src/main/res/drawable | head -10

Repository: LinkYou-2025/LinkU_Android

Length of output: 238

중복된 경로 요소 제거 필요

Lines 24-29와 Lines 39-44에 정확히 동일한 pathData와 fillColor를 가진 경로가 중복 정의되어 있습니다:

오른쪽 볼 (lines 25, 40): M33,25C33,26.105... (#CFCFCF)

왼쪽 볼 (lines 28, 43): M17,25C17,26.105... (#CFCFCF)

동일한 모양과 색상이 두 번 렌더링되고 있으므로, 중복된 path 요소(lines 39-44)를 제거하세요.

🤖 Prompt for AI Agents

In `@feature/home/src/main/res/drawable/ic_anger_gray.xml` around lines 24 - 29, Remove the duplicated circle path elements that repeat the same android:pathData and android:fillColor; specifically find the path elements with android:pathData="M33,25C33,26.105 31.657,27 30,27C28.343,27 27,26.105 27,25C27,23.895 28.343,23 30,23C31.657,23 33,23.895 33,25Z" and android:pathData="M17,25C17,26.105 15.657,27 14,27C12.343,27 11,26.105 11,25C11,23.895 12.343,23 14,23C15.657,23 17,23.895 17,25Z" where they appear twice, and delete the second occurrences (the duplicates) while keeping a single instance of each path with android:fillColor="#CFCFCF".

coderabbitai · 2026-01-28T09:43:38Z

feature/home/src/main/res/drawable/ic_irritation_gray.xml

+          android:type="linear">
+        <item android:offset="0" android:color="#FFCDCDCD"/>
+        <item android:offset="0" android:color="#FFD8D8D8"/>
+        <item android:offset="1" android:color="#FFF3F3F3"/>
+      </gradient>


⚠️ Potential issue | 🟡 Minor

중복된 gradient offset 값

Line 19와 20에서 android:offset="0"이 중복 사용되고 있습니다. 동일한 offset 값을 가진 gradient stop이 두 개 있으면 하나만 적용됩니다. 의도된 gradient 효과를 위해 offset 값을 수정해 주세요.

🔧 제안된 수정

android:type="linear"> - <item android:offset="0" android:color="#FFCDCDCD"/> - <item android:offset="0" android:color="#FFD8D8D8"/> + <item android:offset="0" android:color="#FFCDCDCD"/> + <item android:offset="0.5" android:color="#FFD8D8D8"/> <item android:offset="1" android:color="#FFF3F3F3"/> </gradient>

또는 중복된 색상 stop이 불필요하다면 제거를 고려해 주세요:

android:type="linear"> - <item android:offset="0" android:color="#FFCDCDCD"/> - <item android:offset="0" android:color="#FFD8D8D8"/> + <item android:offset="0" android:color="#FFD8D8D8"/> <item android:offset="1" android:color="#FFF3F3F3"/> </gradient>

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

android:type="linear">

<item android:offset="0" android:color="#FFCDCDCD"/>

<item android:offset="0" android:color="#FFD8D8D8"/>

<item android:offset="1" android:color="#FFF3F3F3"/>

</gradient>

android:type="linear">

<item android:offset="0" android:color="#FFCDCDCD"/>

<item android:offset="0.5" android:color="#FFD8D8D8"/>

<item android:offset="1" android:color="#FFF3F3F3"/>

</gradient>

🤖 Prompt for AI Agents

In `@feature/home/src/main/res/drawable/ic_irritation_gray.xml` around lines 18 - 22, gradient 요소 내에 같은 android:offset="0"이 두 번 사용되어 중복된 스탑이 무시됩니다; gradient 태그(gradient)를 찾아 item 요소들(현재 두 개의 android:offset="0"을 가진 item)을 수정하여 의도된 그라데이션이 나오도록 하나의 offset을 변경(예: 첫째를 0, 둘째를 0.5 등으로 조정)하거나 중복된 색상 stop이 불필요하면 해당 item을 삭제하여 중복을 제거하세요.

ugmin1030 · 2026-01-28T09:44:17Z

feature/home/src/main/java/com/example/home/screen/HomeScreen.kt


-    var isTopBarExpanded by remember { mutableStateOf(true) }
+    var showRecs by remember { mutableStateOf(showRecommendations) }
+    LaunchedEffect(showRecommendations) { showRecs = showRecommendations }


없어도 될 듯?

ugmin1030 · 2026-01-28T09:46:18Z

feature/home/src/main/java/com/example/home/screen/HomeScreen.kt

-        jobSituations.firstOrNull { it.id == selectedTask }?.name
-    }
+    val density = LocalDensity.current
+    val collapseThresholdPx = remember(density) { with(density) { 20.dp.roundToPx() } }


dp로 바꿀 수 있으면 바꿔줘

ugmin1030 · 2026-01-28T09:53:43Z

feature/home/src/main/java/com/example/home/screen/HomeScreen.kt

-        3 -> if (isExpanded) 0.28f else 0.22f
-        else -> 0f
+    // firstVisibleItemIndex>0 이면 이미 헤더가 올라간 상태라 무조건 접힘
+    val collapsedByScroll = remember(


remember -> LaunchedEffect, listState.firstVisibleItemIndex > 0 ||
... 값을 isTopBarLockedCollapsed 대입하는 식으로

ugmin1030 · 2026-01-28T09:57:30Z

feature/home/src/main/java/com/example/home/screen/HomeScreen.kt

-        }
-    }
+    // 고정 접힘이 우선
+    val topBarCollapsed = isTopBarLockedCollapsed || collapsedByScroll


remember를 LaunchedEffect로 수정했으면, collapsedByScroll를 isTopBarLockedCollapsed로 수정

ugmin1030 · 2026-01-28T10:20:04Z

feature/home/src/main/java/com/example/home/ui/top/bar/HomeTopBar.kt

            )
            .background(LocalColorTheme.current.white)
-            .padding(horizontal = 16.dp, vertical = 20.dp)
+            .padding(horizontal = 16.dp, vertical = 13.5.dp)


padding(left = 16.dp, right = 16.dp, top = 20.dp, bottom = 13.5.dp)
그리고 Spacer 없애기

Hongji03 added 6 commits January 14, 2026 16:27

💄 maincolor background 버전 색 추가

62470f6

💄 EmotionSelector 선택 시 뒷배경 그라데이션으로 변경

9b0fa2f

💄 TaskSelector 선택 시 뒷배경 그라데이션으로 변경

a30ca46

💄 TaskSelector 뒷배경 radius 값 수정

f650073

💄 Home Topbar QA 진행

57d944c

🐛 Home Topbar 위로 안접히는 버그 해결

6055ad0

coderabbitai bot reviewed Jan 28, 2026

View reviewed changes

ugmin1030 reviewed Jan 28, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Feature/#43 #75

Feature/#43 #75

Uh oh!

Hongji03 commented Jan 28, 2026 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Jan 28, 2026 •

edited

Loading

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Jan 28, 2026

Uh oh!

coderabbitai bot Jan 28, 2026

Uh oh!

coderabbitai bot Jan 28, 2026

Uh oh!

coderabbitai bot Jan 28, 2026

Uh oh!

coderabbitai bot Jan 28, 2026

Uh oh!

ugmin1030 Jan 28, 2026

Uh oh!

ugmin1030 Jan 28, 2026

Uh oh!

ugmin1030 Jan 28, 2026

Uh oh!

ugmin1030 Jan 28, 2026

Uh oh!

ugmin1030 Jan 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Feature/#43 #75

Are you sure you want to change the base?

Feature/#43 #75

Uh oh!

Conversation

Hongji03 commented Jan 28, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📝 설명

✔️ PR 유형

📎 관련 이슈 번호

Summary by CodeRabbit

릴리스 노트

Uh oh!

coderabbitai bot commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

워크스루

변경 사항

예상 코드 리뷰 노력

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

ugmin1030 Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

ugmin1030 Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

ugmin1030 Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

ugmin1030 Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

ugmin1030 Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Hongji03 commented Jan 28, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Jan 28, 2026 •

edited

Loading