Skip to content

Conversation

XDdevv
Copy link
Contributor

@XDdevv XDdevv commented Aug 19, 2025

Overview

This PR sets the surfaceTint color in the TV ColorScheme (light mode) using primaryLight, which follows Material3 guidance for surface elevation tint. This allows us to remove the TODO comment.

What Changed

  • Added surfaceTint = primaryLight in the TV lightColorScheme
  • Also added surfaceTint to dark mode to keep symmetry
  • Removed the TODO comment

Why

Material3 expects surfaceTint to be specified for elevation tinting. Using the primary color is a standard default in Material guidelines.

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.

Summary of Changes

Hello @XDdevv, 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 enhances the TV ColorScheme by explicitly setting the "surfaceTint" property for both light and dark modes. This change aligns the application with Material3 guidelines, which recommend specifying "surfaceTint" for proper surface elevation tinting. By implementing this, a previous "TODO" comment in the code has been resolved and removed, improving code clarity and maintainability.

Highlights

  • Material3 Compliance: Implemented "surfaceTint" in the TV "ColorScheme" to adhere to Material3 guidelines for surface elevation tinting.
  • Color Scheme Updates: Configured "surfaceTint" to use "primaryLight" for light mode and "primaryDark" for dark mode, ensuring consistency and symmetry across themes.
  • Code Cleanup: Removed a "TODO" comment related to specifying "surfaceTint", indicating completion of the task.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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

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 correctly adds the surfaceTint color to both the light and dark TV ColorSchemes, following Material3 guidelines and resolving a TODO. The changes are sound. I've added a couple of suggestions to improve code consistency by reordering the newly added properties to group them with other related surface* properties. This will enhance readability and maintainability.

Comment on lines 83 to 85
secondary = secondaryDark,
surfaceTint = primaryDark,
onSecondary = onSecondaryDark,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For consistency with the darkColorScheme function signature and to improve readability, surfaceTint should be grouped with the other surface* properties. Please remove it from here and add surfaceTint = primaryDark, after onSurfaceVariant = onSurfaceVariantDark (around line 99).

Suggested change
secondary = secondaryDark,
surfaceTint = primaryDark,
onSecondary = onSecondaryDark,
secondary = secondaryDark,
onSecondary = onSecondaryDark,

Comment on lines 127 to 131
surface = surfaceLight,
surfaceTint = primaryLight,
onSurface = onSurfaceLight,
surfaceVariant = surfaceVariantLight,
onSurfaceVariant = onSurfaceVariantLight,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

To maintain consistency with the function signature of lightColorScheme and improve readability, it's best to place surfaceTint after all other surface* properties.

Suggested change
surface = surfaceLight,
surfaceTint = primaryLight,
onSurface = onSurfaceLight,
surfaceVariant = surfaceVariantLight,
onSurfaceVariant = onSurfaceVariantLight,
surface = surfaceLight,
onSurface = onSurfaceLight,
surfaceVariant = surfaceVariantLight,
onSurfaceVariant = onSurfaceVariantLight,
surfaceTint = primaryLight,

@riggaroo riggaroo requested a review from pflammertsma August 20, 2025 10:57
@XDdevv
Copy link
Contributor Author

XDdevv commented Aug 23, 2025

@riggaroo @pflammertsma 🙂

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.

1 participant