Skip to content

Conversation

@MapleSyrupy
Copy link
Collaborator

No description provided.

@gemini-code-assist
Copy link

Summary of Changes

Hello @MapleSyrupy, 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 primarily focuses on enhancing the user interface of benchmark listings by integrating a newly developed Chips component from the design system. This change standardizes the presentation of various benchmark data points, such as creation dates, levels, and trial counts, making the information more visually appealing and easier to digest. Additionally, it includes minor code cleanup and a layering fix for breadcrumbs to improve overall UI consistency and functionality.

Highlights

  • New Design System Component: Introduced a new reusable Chips component into the design system, wrapping Material-UI's Chip for consistent UI elements across the application.
  • Benchmark UI Enhancement: Refactored the BenchmarkListElement to utilize the new Chips component for displaying key benchmark information such as creation date, benchmark index, baseline, target, and current levels, and number of trials. This significantly improves visual consistency and readability.
  • Improved Data Presentation: Implemented conditional rendering for benchmark levels and trial counts within the Chips component, displaying '0%' or '0' with a distinct default style when data is unavailable, providing clearer feedback than 'N/A'.
  • Storybook Integration: Added Storybook stories for the new Chips component, showcasing its primary and default (empty) states for easy development, testing, and documentation.
  • Layout Z-Index Fix: Adjusted the z-index for breadcrumbs in the main layout to ensure they are always visible and layered correctly above other UI elements.
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.

Copy link

@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 introduces a new Chips component to enhance the UI for displaying benchmark information, which is a great improvement. My review focuses on improving the new component's naming for clarity, fixing a potential typo in the Storybook file, addressing some logic changes in data presentation that might lead to misinterpretation, and general code cleanup. Overall, the changes are positive, and with a few adjustments, the code will be even more robust and maintainable.

Comment on lines 162 to 178
{benchmark?.number_of_trials ? (
<Chips
label={benchmark?.number_of_trials}
color="primary"
size="medium"
></Chips>
) : (
<Chips
label={"0"}
color="default"
size="medium"
sx={{
border: "1px solid",
borderColor: "primary",
}}
></Chips>
)}

Choose a reason for hiding this comment

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

high

Similar to current_level, the logic for number_of_trials has changed to display "0" instead of "N/A" for falsy values. This could be misleading if a null value means 'Not Applicable'. The previous logic || "N/A" was also flawed for a value of 0. It's better to explicitly check for null or undefined to decide whether to show the value or "N/A".

Suggested change
{benchmark?.number_of_trials ? (
<Chips
label={benchmark?.number_of_trials}
color="primary"
size="medium"
></Chips>
) : (
<Chips
label={"0"}
color="default"
size="medium"
sx={{
border: "1px solid",
borderColor: "primary",
}}
></Chips>
)}
{benchmark?.number_of_trials != null ? (
<Chips
label={benchmark.number_of_trials}
color="primary"
size="medium"
/>
) : (
<Chips
label={"N/A"}
color="default"
size="medium"
sx={{
border: "1px solid",
borderColor: "primary",
}}
/>
)}

label: "Primary Chip",
sx: {
border: "1px solid",
borderColor: "Primary",

Choose a reason for hiding this comment

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

medium

The value for borderColor is "Primary" with a capital 'P'. CSS property values and theme keys are typically lowercase. This is likely a typo and should be "primary" to match the usage in other parts of the application (e.g., BenchmarkListElement.tsx).

Suggested change
borderColor: "Primary",
borderColor: "primary",

@francisli
Copy link
Contributor

Screenshot 2025-10-02 at 4 29 52 PM Screenshot 2025-10-02 at 4 30 09 PM

Note styling differences to be corrected...

@MapleSyrupy MapleSyrupy self-assigned this Oct 3, 2025
@MapleSyrupy
Copy link
Collaborator Author

Changed the code to align more with the Figma designs, but there might still be some issues especially with the icons on the buttons to add or view targets.

@MapleSyrupy
Copy link
Collaborator Author

Don't check, not completed, just committing for the sake of saving it. I still need to check it over for any potential styling problems. Also forgot to run prettier on a file.

Copy link
Contributor

@francisli francisli left a comment

Choose a reason for hiding this comment

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

@MapleSyrupy I've added more comments and change requests, we can discuss on the call today if you're available.

Copy link
Contributor

@francisli francisli left a comment

Choose a reason for hiding this comment

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

I think this is looking good to merge now...

I made and pushed up an additional change- since you added the new "startIcon" prop to our design system Button, I added corresponding stories to preview how that looks in storybook across all variants. I then used that to tweak the layout a bit so that the icon is centered with the button label text.

@francisli francisli merged commit a4b2c3b into main Oct 30, 2025
4 checks passed
@francisli francisli deleted the BenchmarkUIChips branch October 30, 2025 22:01
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