Skip to content

Updates modifiers used in Wear M3 1.6.0#845

Merged
garanj merged 3 commits intomainfrom
wear-minimumVerticalContentPadding
Mar 20, 2026
Merged

Updates modifiers used in Wear M3 1.6.0#845
garanj merged 3 commits intomainfrom
wear-minimumVerticalContentPadding

Conversation

@garanj
Copy link
Contributor

@garanj garanj commented Mar 20, 2026

Migrates TransformingLazyColumn examples to 1.6.0 (rc01) of Wear Compose.

Specifically:

  • Using minimumVerticalContentPadding to correctly set the list padding top and bottom
  • Using snapFlingBehavior to demonstrate snapping

@garanj garanj requested review from a team, kkuan2011 and yrezgui as code owners March 20, 2026 13:44
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 updates the Wear Compose M3 examples to align with the 1.6.0-rc01 release. The primary goal is to showcase the new minimumVerticalContentPadding modifier for proper list item spacing and to demonstrate the snapFlingBehavior for TransformingLazyColumn, ensuring the examples reflect the latest API changes and best practices.

Highlights

  • Wear Compose M3 Version Update: Updated Wear Compose M3 libraries to version 1.6.0-rc01 across the project dependencies.
  • Content Padding Refinement: Implemented minimumVerticalContentPadding modifier for ListHeader and Button components within TransformingLazyColumn to correctly set list padding.
  • Snap Fling Behavior Demonstration: Demonstrated the use of snapFlingBehavior with TransformingLazyColumn for improved scrolling interaction.
  • Horologist API Removal: Removed dependencies and usage of the Horologist library in the list examples, migrating to native Wear Compose M3 components.

🧠 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request successfully migrates the TransformingLazyColumn examples to use the new APIs from Wear Compose 1.6.0, removing dependencies on Horologist. The changes correctly adopt minimumVerticalContentPadding and snapFlingBehavior. I have one suggestion to improve the consistency of an example snippet.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@garanj garanj requested a review from ithinkihaveacat March 20, 2026 14:17
@garanj garanj enabled auto-merge (squash) March 20, 2026 16:18
@garanj garanj merged commit ebfa59e into main Mar 20, 2026
6 checks passed
@garanj garanj deleted the wear-minimumVerticalContentPadding branch March 20, 2026 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants