feat: 리워드 화면 사용 가능 온도 설명 텍스트 추가 및 카메라 화면 설명 텍스트 굵기 변경

[surfwithus]

Important

UI text updates in add_record_screen.dart and reward_screen.dart for improved clarity and styling.

• Add Record Screen:
  • Change font weight of description text from w400 to w500 in AddRecordScreenState.
• Reward Screen:
  • Add new description text about usable temperature in _RewardScreenState.
  • Change withOpacity to withValues for shadowDarkColorEmboss in NeumorphicStyle.
  • Increase height of SizedBox from 90 to 100 in _RewardScreenState.

^{This description was created by for 618401b. You can customize this summary. It will automatically update as commits are pushed.}

Summary by CodeRabbit

• 신기능
  • 보상 화면 온도 표시 영역에 안내 문구 추가: “기본 온도 36.5℃를 제외한 실제 사용 가능 온도예요!”(우하단 정렬의 소형 캡션)
• 스타일
  • 추가/기록 화면의 작은 텍스트 가독성 향상을 위해 글자 두께 상향
  • 보상 화면 온도 카드 높이를 90→100으로 조정해 레이아웃 균형 개선
  • 반투명 색상 표현을 정밀화해 대비 및 시인성 개선

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

이 PR은 두 개의 Flutter 화면에서 순수 UI 스타일 변경을 수행합니다. AddRecordScreen의 텍스트 굵기를 조정했고, RewardScreen에서 색상 알파 API를 교체하고 컨테이너 높이를 키우며 설명 캡션 텍스트를 추가했습니다. 로직, 제어 흐름, 공개 API 변경은 없습니다.

Changes

Cohort / File(s)	Summary
타이포그래피 미세 조정 frontend/ongi/lib/screens/add_record_screen.dart	특정 12pt Text 위젯의 fontWeight를 w400에서 w500으로 변경. 기능/로직 변화 없음.
리워드 화면 UI 업데이트 frontend/ongi/lib/screens/reward_screen.dart	withOpacity(0.9)를 withValues(alpha: 0.9)로 교체, Neumorphic 컨테이너 높이 90→100, 하단 우측에 소형 안내 캡션 텍스트 추가(“기본 온도 36.5℃…”, fs 9, w400, h 1.0, black54).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat: 마음 기록 화면 완성 #58: 동일한 AddRecordScreen 구현을 수정한 PR로, 이번 PR의 텍스트 스타일 조정과 같은 파일을 다루므로 코드 레벨에서 연관성이 높습니다.

Poem

봄빛 코드를 살짝 다듬는 발자국,\n>
w400에서 w500으로 콩콩—리듬이 쫀득!\n>
리워드 상자도 쑥—높이 한 칸 업,\n>
알파는 새 길로, 속삭임 캡션 톡.\n>
토끼는 귀를 씰룩, “UI가 한층 푹!” 🐰✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between c216d00 and 618401b.

📒 Files selected for processing (2)

• frontend/ongi/lib/screens/add_record_screen.dart (1 hunks)
• frontend/ongi/lib/screens/reward_screen.dart (3 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/reward-text

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 618401b in 1 minute and 55 seconds. Click for details.

• Reviewed 56 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. frontend/ongi/lib/screens/add_record_screen.dart:306

• Draft comment:
  Increased fontWeight from w400 to w500; please ensure this matches the overall design style.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. frontend/ongi/lib/screens/reward_screen.dart:212

• Draft comment:
  Using 'withValues(alpha: 0.9)' is non-standard; verify that this method exists or revert to 'withOpacity(0.9)'.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% 1. The comment claims withValues is non-standard but provides no evidence. 2. This is using a third-party UI package (flutter_neumorphic_plus) which may have its own valid methods. 3. Without seeing the package documentation, I cannot verify if withValues is incorrect. 4. The code compiles and runs since this is a released PR. 5. This appears to be a UI styling concern which we are told to ignore. I may be overlooking a Flutter standard that makes withValues definitively wrong. The code compiling doesn't necessarily mean it's correct. Even if withValues is non-standard, this is a UI styling issue which we're explicitly told to ignore. Additionally, without package documentation we cannot be certain this is incorrect. Delete this comment because it relates to UI styling which we're told to ignore, and we don't have strong evidence that the current code is incorrect.

3. frontend/ongi/lib/screens/reward_screen.dart:220

• Draft comment:
  SizedBox height adjusted from 90 to 100; confirm that the increased height suits the layout.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. frontend/ongi/lib/screens/reward_screen.dart:288

• Draft comment:
  Added explanatory text about available temperature; ensure its styling and placement adhere to the design specs.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. frontend/ongi/lib/screens/reward_screen.dart:213

• Draft comment:
  Typo: 'withValues' is used here. It appears that the standard method is 'withOpacity'; please check if this is a typo.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While .withOpacity() is more common in Flutter, .withValues() is also a valid way to set opacity in Flutter. Without seeing the flutter_neumorphic_plus package source code, I can't be 100% sure which method is preferred here. The code compiles and works as is, and both methods achieve the same result. This seems like a stylistic preference rather than a clear error. I could be wrong about the flutter_neumorphic_plus package's preferred method - maybe .withValues() is actually incorrect in this context. The comment author may have specific knowledge about this package that I don't. Even if .withOpacity() is more standard, the code works as is and the difference is minor. Making this change would not meaningfully improve the code. This comment should be deleted as it suggests a change that is not clearly necessary or beneficial. Both methods work and the difference is stylistic.

Workflow ID: wflow_8FcgEm5vUWX7gIki

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}