Fix incorrect package name in uistateadapter Utils

[helpingstar]

Fixes #423

Summary

• Corrected package name from com.example.uistateadapter to com.google.jetpackcamera.ui.uistateadapter
• Moved Utils.kt file to the correct directory structure
• Updated imports in 4 adapter files

Changes

• Utils.kt: package name and file path correction
• AspectRatioUiStateAdapter.kt: import path update
• FlashModeUiStateAdapter.kt: import path update
• FlipLensUiStateAdapter.kt: import path update
• StreamConfigsUiStateAdapter.kt: import path update

The Utils.kt file was using com.example.* package which is typically a placeholder name. This PR aligns it with the project's standard package structure.

[gemini-code-assist]

Summary of Changes

Hello @helpingstar, 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!

This pull request addresses a structural inconsistency by correcting the package name and file location of a utility file, Utils.kt. The change ensures that the file aligns with the project's established package hierarchy and updates all dependent files to reference the correct path, thereby improving code organization and maintainability.

Highlights

• Package Name Correction: The package name for the Utils.kt file has been updated from com.example.uistateadapter to com.google.jetpackcamera.ui.uistateadapter to adhere to the project's standard naming conventions.
• File Relocation: The Utils.kt file was moved to a new directory structure that correctly reflects its updated package name.
• Import Path Updates: Imports for Utils.kt were adjusted in four adapter files (AspectRatioUiStateAdapter.kt, FlashModeUiStateAdapter.kt, FlipLensUiStateAdapter.kt, and StreamConfigsUiStateAdapter.kt) to point to its new, correct package.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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 correctly addresses the incorrect package name in Utils.kt, moving it from a placeholder com.example package to the project's standard com.google.jetpackcamera.ui.uistateadapter. The import paths in all dependent files have been updated accordingly. The changes are correct and well-executed.

As a suggestion for future improvement, the getSelectableListFromValues function in Utils.kt could be refactored. Its KDoc parameter names are out of sync with the function signature, and the implementation can be made more concise by using a member reference for the .map operation (e.g., .map(SingleSelectableUiState::SelectableUi)). This would improve readability and align with Kotlin best practices, as encouraged by the repository's style guide (lines 22 and 64).