fix(ui): filter out empty history items from being rendered

[devr0306]

Summary

This pull request effectively addresses the issue of empty history items being rendered by filtering them out before they are passed to the UI components.

Details

Empty history items were being rendered which ended up adding extra space above some of the rendered content. This PR fixes that.

Related Issues

Fixes #18452

How to Validate

1. Enter alternate buffer mode and ask "Without calling any tool, show me an example java class"
2. Exit alternate buffer mode and ask the same thing

Both cases should display content without extra spaces

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello @devr0306, 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 user interface rendering anomaly where empty history items were inadvertently displayed, leading to unnecessary vertical spacing. By implementing a filtering mechanism, the application now correctly omits these empty entries, resulting in a cleaner and more compact display of historical content.

Highlights

• UI Rendering Fix: Empty history items, specifically 'gemini_content' with no text, are now filtered out to prevent them from being rendered.
• Space Reduction: This change resolves an issue where empty history items caused extra vertical space above rendered content in the UI.

Changelog

• packages/cli/src/ui/components/MainContent.test.tsx
  • Added a new test case to verify that empty history items are not rendered.
• packages/cli/src/ui/components/MainContent.tsx
  • Implemented a filter within the 'historyItems' useMemo hook to exclude 'gemini_content' items that have no text.
  • Applied the same filtering logic to the 'virtualizedData' useMemo hook to ensure empty history items are not included in the virtualized list.
• packages/cli/src/ui/components/snapshots/MainContent.test.tsx.snap
  • Updated the snapshot to reflect the new test case for not rendering empty history items.
• packages/cli/src/ui/utils/MarkdownDisplay.tsx
  • Corrected a typo from "to long" to "too long" in a comment.

Activity

• The author has added a new test case to validate the fix for empty history items.
• The author has validated the changes on MacOS using 'npm run'.
• Instructions for validating the fix have been provided, including steps to reproduce the original issue and confirm its resolution in both alternate buffer mode and regular mode.

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 effectively addresses the issue of empty history items being rendered by filtering them out before they are passed to the UI components. The addition of a new test case ensures this behavior is covered and prevents regressions. My main feedback is to refactor the duplicated filtering logic into a separate useMemo hook to improve code maintainability and reduce the chance of future bugs.

[devr0306]

From /review-frontend:

LGTM! The fix effectively filters out empty history items, resolving the extra spacing issue. The added test case correctly verifies this behavior using the established testing patterns. Thanks for the cleanup in MarkdownDisplay.tsx as well.

[github-actions]

Size Change: +167 B (0%)

Total Size: 24.4 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	24.4 MB	+167 B (0%)
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B
./bundle/sandbox-macos-strict-open.sb	4.82 kB	0 B
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB	0 B

_{compressed-size-action}