fix: [adapter] 表格配置类型报错

[wdzyy]

配置toolbarConfig中的search时会有类型报错

Description

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Refactor
  • Improved type safety for grid configuration options to enhance reliability and maintainability. No changes to user-facing features or functionality.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d88b395

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Explicit TypeScript type assertions were added to the grid configuration objects passed to vxeUI.setConfig in several adapter files. The objects are now cast as VxeTableGridOptions to enforce type checking. No runtime or control flow changes were introduced.

Changes

Files	Change Summary
apps/web-antd/src/adapter/vxe-table.ts apps/web-ele/src/adapter/vxe-table.ts apps/web-naive/src/adapter/vxe-table.ts playground/src/adapter/vxe-table.ts	Added explicit type assertion (as VxeTableGridOptions) to the grid object passed to vxeUI.setConfig for stronger type checking.

Possibly related issues

• FEATURE: 为vxe-grid添加泛型,使其更加符合开发需要 #6326: Both the PR and the issue address type safety improvements for vxe-grid configuration, making this PR relevant to the issue.

Suggested reviewers

• mynetfan
• anncwb
• jinmao88

Poem

In the warren where TypeScript hops,
Rabbits add types—no runtime flops!
With VxeTableGridOptions in tow,
Our grids are safe, as code will show.
Stronger types, less fright—
Bugs beware, we code it right!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ea776aa and d88b395.

📒 Files selected for processing (4)

• apps/web-antd/src/adapter/vxe-table.ts (2 hunks)
• apps/web-ele/src/adapter/vxe-table.ts (2 hunks)
• apps/web-naive/src/adapter/vxe-table.ts (2 hunks)
• playground/src/adapter/vxe-table.ts (2 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (4)

apps/web-naive/src/adapter/vxe-table.ts (1)

packages/effects/plugins/src/vxe-table/types.ts (1)

• VxeTableGridOptions (29-32)

apps/web-antd/src/adapter/vxe-table.ts (1)

packages/effects/plugins/src/vxe-table/types.ts (1)

• VxeTableGridOptions (29-32)

apps/web-ele/src/adapter/vxe-table.ts (1)

packages/effects/plugins/src/vxe-table/types.ts (1)

• VxeTableGridOptions (29-32)

playground/src/adapter/vxe-table.ts (1)

packages/effects/plugins/src/vxe-table/types.ts (1)

• VxeTableGridOptions (29-32)

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

• GitHub Check: Check (windows-latest)
• GitHub Check: Test (windows-latest)
• GitHub Check: Lint (windows-latest)
• GitHub Check: post-update (windows-latest)
• GitHub Check: post-update (ubuntu-latest)

🔇 Additional comments (8)

apps/web-antd/src/adapter/vxe-table.ts (2)

1-1: LGTM! Proper type import added.

The import of VxeTableGridOptions provides the necessary TypeScript type for the grid configuration.

---

38-38: LGTM! Type assertion resolves configuration type safety.

The explicit type assertion as VxeTableGridOptions ensures the grid configuration object conforms to the expected interface, which should resolve the type error mentioned in the PR objectives related to table configuration.

playground/src/adapter/vxe-table.ts (2)

1-1: LGTM! Consistent type import across adapters.

The import statement properly brings in the VxeTableGridOptions type definition for type safety.

---

46-46: LGTM! Type assertion maintains consistency.

The type assertion is consistent with other adapter files and properly ensures the grid configuration conforms to the expected VxeTableGridOptions interface.

apps/web-naive/src/adapter/vxe-table.ts (2)

1-1: LGTM! Type import maintains cross-adapter consistency.

The import correctly adds the VxeTableGridOptions type, maintaining consistency with other adapter implementations.

---

38-38: LGTM! Type assertion ensures proper configuration typing.

The type assertion correctly enforces type safety for the grid configuration object, resolving potential type errors with the table configuration.

apps/web-ele/src/adapter/vxe-table.ts (2)

1-1: LGTM! Completes consistent typing across all adapters.

The import statement properly adds the necessary type definition, completing the consistent type safety implementation across all VXE Table adapters.

---

38-38: LGTM! Final type assertion completes the fix.

The type assertion correctly ensures the grid configuration conforms to VxeTableGridOptions, which should resolve the table configuration type errors mentioned in the PR objectives. All adapter files now have consistent type safety.

✨ 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

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