fix: should pass colGroup

[li-jia-nan]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
table	Ready	Preview	Comment	Sep 15, 2025 7:01am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snap-up

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @li-jia-nan, 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 focuses on maintaining the integrity of the test suite by updating a snapshot. The change ensures that the automated tests accurately reflect the current and intended rendering behavior of the FixedColumn component, specifically regarding its table structure. This is a routine update to align the test expectations with recent code modifications, preventing false test failures.

Highlights

• Test Snapshot Update: The pull request updates the snapshot for FixedColumn.spec.tsx to reflect changes in the component's rendering output.
• HTML Structure Change: The <colgroup> and its nested <col> elements have been removed from the expected rendered HTML output in the snapshot, indicating these elements are no longer generated by the component under test.

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

[gemini-code-assist]

Code Review

This pull request solely updates a test snapshot, which involves removing a <colgroup> element from the rendered output of a table component. This is a significant structural change to the generated HTML. While using table-layout: fixed allows the browser to determine column widths from the first row of cells, removing the <colgroup> may have performance implications, as it's a more direct way for the browser to understand column layout, potentially leading to slower render times for complex tables.

[afc163]

为啥 snap 会变？

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.75%. Comparing base (6994837) to head (1ee3ba0).
⚠️ Report is 16 commits behind head on antd-5.x.

Additional details and impacted files

@@             Coverage Diff              @@
##           antd-5.x    #1356      +/-   ##
============================================
+ Coverage     97.74%   97.75%   +0.01%     
============================================
  Files            77       77              
  Lines          7626     7666      +40     
  Branches       1154     1163       +9     
============================================
+ Hits           7454     7494      +40     
  Misses          166      166              
  Partials          6        6              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[li-jia-nan]

为啥 snap 会变？

修了