Skip to content

fix(grid): increase the length of drag and drop lines in the grid and remove empty values when filtering #3475

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 4, 2025

Conversation

wuyiping0628
Copy link
Collaborator

@wuyiping0628 wuyiping0628 commented Jun 4, 2025

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

  • Bug Fixes

    • Filter input values now automatically remove leading and trailing whitespace before applying filters, improving accuracy and consistency.
  • Style

    • The table grid's vertical resize handle is now thinner and uses the brand color, providing a more refined and visually consistent appearance.

@wuyiping0628 wuyiping0628 added the enhancement New feature or request (功能增强) label Jun 4, 2025
Copy link

coderabbitai bot commented Jun 4, 2025

Walkthrough

The changes update the visual styling of the table grid's resizable bar by adjusting its width and color in LESS files. Additionally, the filter panel logic is improved to trim whitespace from user input before applying the filter, ensuring cleaner and more accurate filtering. The dynamic columns test was also updated to reflect changed month text formats and more precise visibility assertions.

Changes

File(s) Change Summary
packages/theme-saas/src/grid/table-global.less,
packages/theme-saas/src/grid/table.less
Updated resizable bar width from w-px to w-0.5 and changed background color to brand color.
packages/vue/src/grid/src/filter/src/panel.tsx Added trimming of whitespace to filter input before applying the filter condition.
examples/sites/demos/pc/app/grid/dynamically-columns/dynamically-columns.spec.js Modified month text selectors from Chinese characters to numeric format and refined visibility assertion.

Poem

A thinner line, a brighter hue,
The table grid feels fresh and new!
Filters now are crisp and neat—
No extra spaces to defeat.
With every tweak, the grid refines,
As rabbits hop between the lines! 🐇

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

examples/sites/demos/pc/app/grid/dynamically-columns/dynamically-columns.spec.js

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

packages/vue/src/grid/src/filter/src/panel.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.

@github-actions github-actions bot added bug Something isn't working and removed enhancement New feature or request (功能增强) labels Jun 4, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9f3626d and e6a34d6.

📒 Files selected for processing (3)
  • packages/theme-saas/src/grid/table-global.less (1 hunks)
  • packages/theme-saas/src/grid/table.less (1 hunks)
  • packages/vue/src/grid/src/filter/src/panel.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)
🔇 Additional comments (3)
packages/theme-saas/src/grid/table-global.less (2)

633-633: Width increase improves visibility of the resizable bar.

The change from w-px (1px) to w-0.5 (2px) makes the resizable bar thicker, improving its visibility for users during drag and drop operations. This aligns well with the PR objective.


641-641: Brand color enhances visual consistency.

Changing the resizable bar color to bg-color-brand improves visual consistency with the design system and makes the drag indicator more prominent.

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

724-724: Consistent styling improvements across theme files.

The width and color changes are identical to those in table-global.less, ensuring consistent appearance of the resizable bar across different theme contexts. The thicker width (2px instead of 1px) and brand color enhance usability and visual consistency.

Also applies to: 732-732

@wuyiping0628 wuyiping0628 changed the title fix(grid): increase the length of drag and drop lines and remove empty values when filtering fix: increase the length of drag and drop lines and remove empty values when filtering Jun 4, 2025
@wuyiping0628 wuyiping0628 changed the title fix: increase the length of drag and drop lines and remove empty values when filtering fix: increase the length of drag and drop lines in the grid and remove empty values when filtering Jun 4, 2025
@wuyiping0628 wuyiping0628 changed the title fix: increase the length of drag and drop lines in the grid and remove empty values when filtering fix(grid): increase the length of drag and drop lines in the grid and remove empty values when filtering Jun 4, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
examples/sites/demos/pc/app/grid/dynamically-columns/dynamically-columns.spec.js (1)

7-8: Consider making date selection more robust.

The updated month selectors reflect the UI changes well, but the use of .nth(2) for February selection suggests multiple matching elements, which could make the test brittle.

Consider using more specific selectors or adding data-testid attributes to make the test more reliable:

-  await page.getByText('12 月').first().click()
-  await page.getByText('2 月').nth(2).click()
+  await page.getByTestId('month-december').click()
+  await page.getByTestId('month-february-option-3').click()

Alternatively, if data-testid attributes aren't feasible, consider adding assertions to validate the selection state:

  await page.getByText('12 月').first().click()
+  await expect(page.getByText('12 月').first()).toHaveClass(/selected|active/)
  await page.getByText('2 月').nth(2).click()
+  await expect(page.getByText('2 月').nth(2)).toHaveClass(/selected|active/)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 28281bf and 43ba6f2.

📒 Files selected for processing (2)
  • examples/sites/demos/pc/app/grid/dynamically-columns/dynamically-columns.spec.js (1 hunks)
  • packages/vue/src/grid/src/filter/src/panel.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/vue/src/grid/src/filter/src/panel.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)
🔇 Additional comments (1)
examples/sites/demos/pc/app/grid/dynamically-columns/dynamically-columns.spec.js (1)

9-9: Good improvement for test determinism.

Adding .first() to the visibility assertion makes the test more specific and less prone to false positives when multiple cells with the same name exist.

@zzcr zzcr merged commit 965dcdd into dev Jun 4, 2025
8 of 10 checks passed
@zzcr zzcr deleted the wyp/grid--tirm-0603 branch June 4, 2025 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants