🚀 :: Release/1.7.0-18

[khs3994]

💡 개요

• deploy: 1.7.0 (18)

📃 작업내용

• 알레르기 기능 추가

🔀 변경사항

🎸 기타

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 780b40ac-70ec-4e21-948d-6909ea61d19d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.7.0-18

---

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

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

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

이 PR은 애플리케이션에 새로운 알레르기 관리 기능을 도입합니다. 이제 사용자는 특정 알레르기를 선택할 수 있으며, 애플리케이션은 해당 알레르기 유발 물질을 포함하는 급식 항목을 강조 표시합니다. 이 개선 사항은 급식 정보 표시 내에서 개인화된 식단 정보를 제공하여 사용자 경험을 향상시키며, 애플리케이션 버전이 1.7.0으로 업데이트되었습니다.

Highlights

• 알레르기 기능 구현: 사용자가 자신의 알레르기를 선택하고 관리할 수 있는 새로운 알레르기 기능이 추가되었습니다.
• 급식 항목 알레르기 정보 표시: 급식 항목에 알레르기 ID가 포함되도록 변경되었으며, 사용자가 선택한 알레르기 유발 식품은 급식 UI에서 시각적으로 강조 표시됩니다.
• 버전 업데이트: 애플리케이션 버전이 1.7.0 (버전 코드 18)로 업데이트되었습니다.
• 알레르기 데이터 영속성: DataStore를 활용하여 선택된 알레르기 ID를 로컬에 저장하고 검색하는 데이터 소스 및 저장소 계층이 추가되었습니다.
• UI 컴포넌트 리팩토링 및 신규 모듈 추가: AllergiesCard 컴포넌트가 DrawableRes를 사용하여 아이콘을 처리하도록 리팩토링되었고, 알레르기 관련 UI 및 로직을 위한 feature/allergies 모듈이 새로 추가되었습니다.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new allergy settings feature, allowing users to select their allergies. This involved significant refactoring of meal data handling to include allergy information, transitioning from simple lists of strings to a MealMenuItem data class that encapsulates both the meal name and associated allergy IDs. A new AllergiesCard component was created, and existing meal display components were updated to highlight meals containing selected allergens. Data persistence for selected allergies is handled via DataStore. The PR also updates the app version and adds a .omc entry to .gitignore. A potential issue was identified where the catch operator in the getSelectedAllergyIdsUseCase flow could terminate the flow collection on error, leading to stale allergy data on the main screen until the ViewModel is recreated.

[gemini-code-assist]

The catch operator here will cause the flow collection to terminate upon any exception from the upstream getSelectedAllergyIdsUseCase() flow (e.g., an IOException from DataStore). While it correctly sets a default emptySet(), the flow will no longer be collected after an error. This means if the user navigates to settings, changes their allergies, and returns to the main screen, the changes will not be reflected because the flow is no longer being observed. The allergy information will remain stale until the ViewModel is recreated (e.g., on app restart), which can lead to a confusing user experience.