Skip to content

Fix/#164 QA 반영#176

Merged
wotjs020708 merged 3 commits intodevelopfrom
fix/#164-treatmentqa2
Jan 23, 2026
Merged

Fix/#164 QA 반영#176
wotjs020708 merged 3 commits intodevelopfrom
fix/#164-treatmentqa2

Conversation

@wotjs020708
Copy link
Contributor

🔗 연결된 이슈

📄 작업 내용

  • 높이 자동 조절 수정

@wotjs020708 wotjs020708 requested a review from a team January 23, 2026 12:21
@wotjs020708 wotjs020708 self-assigned this Jan 23, 2026
@wotjs020708 wotjs020708 requested review from soseoyo12, sum130 and y-eonee and removed request for a team January 23, 2026 12:21
@wotjs020708 wotjs020708 added Fix 버그 수정 재선🐻 labels Jan 23, 2026
@coderabbitai
Copy link

coderabbitai bot commented Jan 23, 2026

📝 Walkthrough

Walkthrough

치료 필터 뷰의 동적 간격 조정. 선택된 치료 항목이 없을 때와 있을 때를 구분하여 스페이서 높이를 조건부로 설정하는 레이아웃 수정입니다.

Changes

Cohort / File(s) Change Summary
Treatment Filter Layout
NoTreatmentFilterView.swift, TreatmentFilterView.swift
고정된 스페이서 높이를 조건부 높이로 변경. 선택된 치료 항목이 없으면 24.adjustedH, 있으면 scrollViewHeight.adjustedH + 24.adjustedH 적용. 내용의 유무에 따라 하단 여백을 동적으로 조정.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested labels

재선🐻

Suggested reviewers

  • sum130
  • soseoyo12
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed PR 제목은 '#164 QA 반영'으로 연결된 이슈 #164와 관련이 있으며, 변경 사항인 높이 자동 조절 수정을 간접적으로 나타냅니다.
Description check ✅ Passed PR 설명은 높이 자동 조절 수정이라는 구체적인 작업 내용을 포함하고 있으며, 이슈 #164와 연결되어 있습니다.
Linked Issues check ✅ Passed PR은 연결된 이슈 #164의 'QA 수정' 요구사항을 충족하기 위해 NoTreatmentFilterView와 TreatmentFilterView의 높이 자동 조절 로직을 수정했습니다.
Out of Scope Changes check ✅ Passed 모든 변경 사항이 이슈 #164의 높이 자동 조절 수정이라는 범위 내에 있으며, 관련 없는 변경은 없습니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/#164-treatmentqa2

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.

Copy link
Contributor

@y-eonee y-eonee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

어프르브

Copy link
Contributor

@soseoyo12 soseoyo12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

수고하셨습니당

Copy link
Contributor

@sum130 sum130 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

어푸푸푸! 수고했어욤

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In
`@Cherrish-iOS/Cherrish-iOS/Presentation/Feature/Calendar/Treatment/View/NoTreatment/NoTreatmentFilterView.swift`:
- Around line 53-56: The frame height calculation applies the adjustedH scale
twice to scrollViewHeight causing excessive spacing; update the height
expression in the .frame call that uses viewModel.selectedTreatments and
scrollViewHeight so that scrollViewHeight is only scaled once (remove the extra
.adjustedH) and keep adjustedH applied to either scrollViewHeight or the added
constant (24) consistently to avoid double-scaling.

In
`@Cherrish-iOS/Cherrish-iOS/Presentation/Feature/Calendar/Treatment/View/Treatment/TreatmentFilterView.swift`:
- Around line 78-81: The frame height applies .adjustedH twice to
scrollViewHeight; in the TreatmentFilterView replace the double-adjustment by
using scrollViewHeight directly (leave .adjustedH only on the empty case).
Update the .frame(height:) expression that references
viewModel.selectedTreatments and scrollViewHeight so it uses scrollViewHeight
(no .adjustedH) when not empty, keeping the existing 24.adjustedH on the empty
branch.

Comment on lines +53 to +56
.frame(
height: viewModel.selectedTreatments.isEmpty ?
24.adjustedH : scrollViewHeight.adjustedH + 24.adjustedH
)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

scrollViewHeight 이중 스케일링으로 여백이 과해질 수 있습니다.

Line 53-56에서 scrollViewHeight 계산에 이미 adjustedH가 포함되어 있는데 다시 .adjustedH를 적용해 크기가 과장될 가능성이 있습니다. 동일하게 한 번만 적용해주세요.

🛠️ 수정 제안
-                        .frame(
-                            height: viewModel.selectedTreatments.isEmpty ?
-                            24.adjustedH : scrollViewHeight.adjustedH + 24.adjustedH
-                        )
+                        .frame(
+                            height: viewModel.selectedTreatments.isEmpty ?
+                            24.adjustedH : scrollViewHeight + 24.adjustedH
+                        )
📝 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
.frame(
height: viewModel.selectedTreatments.isEmpty ?
24.adjustedH : scrollViewHeight.adjustedH + 24.adjustedH
)
.frame(
height: viewModel.selectedTreatments.isEmpty ?
24.adjustedH : scrollViewHeight + 24.adjustedH
)
🤖 Prompt for AI Agents
In
`@Cherrish-iOS/Cherrish-iOS/Presentation/Feature/Calendar/Treatment/View/NoTreatment/NoTreatmentFilterView.swift`
around lines 53 - 56, The frame height calculation applies the adjustedH scale
twice to scrollViewHeight causing excessive spacing; update the height
expression in the .frame call that uses viewModel.selectedTreatments and
scrollViewHeight so that scrollViewHeight is only scaled once (remove the extra
.adjustedH) and keep adjustedH applied to either scrollViewHeight or the added
constant (24) consistently to avoid double-scaling.

Comment on lines +78 to +81
.frame(
height: viewModel.selectedTreatments.isEmpty ?
24.adjustedH : scrollViewHeight.adjustedH + 24.adjustedH
)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

scrollViewHeight.adjustedH가 중복 적용됩니다.

Line 78-81에서 scrollViewHeight는 이미 adjustedH를 포함해 계산되므로 다시 .adjustedH를 적용하면 기기별로 간격이 과도하게 늘어날 수 있습니다. scrollViewHeight는 그대로 사용하세요.

🛠️ 수정 제안
-                        .frame(
-                            height: viewModel.selectedTreatments.isEmpty ?
-                            24.adjustedH : scrollViewHeight.adjustedH + 24.adjustedH
-                        )
+                        .frame(
+                            height: viewModel.selectedTreatments.isEmpty ?
+                            24.adjustedH : scrollViewHeight + 24.adjustedH
+                        )
📝 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
.frame(
height: viewModel.selectedTreatments.isEmpty ?
24.adjustedH : scrollViewHeight.adjustedH + 24.adjustedH
)
.frame(
height: viewModel.selectedTreatments.isEmpty ?
24.adjustedH : scrollViewHeight + 24.adjustedH
)
🤖 Prompt for AI Agents
In
`@Cherrish-iOS/Cherrish-iOS/Presentation/Feature/Calendar/Treatment/View/Treatment/TreatmentFilterView.swift`
around lines 78 - 81, The frame height applies .adjustedH twice to
scrollViewHeight; in the TreatmentFilterView replace the double-adjustment by
using scrollViewHeight directly (leave .adjustedH only on the empty case).
Update the .frame(height:) expression that references
viewModel.selectedTreatments and scrollViewHeight so it uses scrollViewHeight
(no .adjustedH) when not empty, keeping the existing 24.adjustedH on the empty
branch.

@wotjs020708 wotjs020708 merged commit af993ff into develop Jan 23, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Fix 버그 수정 재선🐻

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fix] 2차 QA 수정

4 participants

Comments