fix: [grid] Add a scroll bar at the bottom of the SaaS theme table to be placed inside the table, with only one border at the bottom

[chenxi-20]

PR

改前：

改后：

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Style
  • Improved the appearance of tables by adding a subtle horizontal line at the bottom of the last row, enhancing visual separation and containment within the grid component.

[coderabbitai]

Walkthrough

A new CSS rule was introduced to the grid component's table styling. Specifically, the last row within the table body (tbody tr:last-child) now receives a relative positioning context, and a pseudo-element (::after) is added. This pseudo-element creates a 1-pixel-high horizontal line at the bottom of the last row, spanning the full width and using the bg-color-bg-1 background color. No changes were made to any exported or public entities.

Changes

File(s)	Change Summary
packages/theme-saas/src/grid/table.less	Added a CSS rule to style the last table row with a pseudo-element for a bottom horizontal line.

Poem

A line at the bottom, so subtle and neat,
The table now ends with a visual treat.
With pixels aligned and colors just right,
The grid feels contained, a pleasing sight.
CSS magic, a rabbit’s delight!
🐇✨

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/theme-saas/src/grid/table.less (1)

274-289: Eliminate redundant bottom-0 and prevent event interception
The ::after pseudo-element declares @apply bottom-0 twice; you can remove the duplicate and add pointer-events-none so the line won’t block pointer events (e.g., scrolling).

Apply this diff:

@@ 274,289 @@
   tbody tr:last-child {
     @apply relative;

     &::after {
       @apply content-[''];
       @apply absolute;
-      @apply bottom-0;
-      @apply bottom-0;
+      @apply bottom-0;
       @apply left-0;
       @apply right-0;
       @apply h-px;
       @apply bg-color-bg-1;
+      @apply pointer-events-none;
     }
   }

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 666bb0f and e1560fb.

📒 Files selected for processing (1)

• packages/theme-saas/src/grid/table.less (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: PR E2E Test (pnpm test:e2e3)
• GitHub Check: PR Unit Test