Skip to content

docs(vben-form): update the form adapter document - #6656

Merged
jinmao88 merged 1 commit into
vbenjs:mainfrom
qianYuanJ:main
Aug 19, 2025
Merged

jinmao88 merged 1 commit into
vbenjs:mainfrom
qianYuanJ:main

Conversation

@qianYuanJ

@qianYuanJ qianYuanJ commented Aug 19, 2025 •

Copy link
Copy Markdown
Contributor

…ion in the document

Description

update the component import of the form adapter description in the document

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

    • Optimized UI component loading with on‑demand (asynchronous) components, reducing initial load time and bundle size while preserving existing behavior and APIs.
  • Documentation

    • Updated component adapter docs to reflect the new asynchronous loading approach; no changes required for existing integrations.

@changeset-bot

changeset-bot Bot commented Aug 19, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 11dcc71

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

coderabbitai Bot commented Aug 19, 2025 •

Copy link
Copy Markdown
Contributor

Walkthrough

The change replaces static ant-design-vue imports with per-component lazy-loaded async components via defineAsyncComponent using 'ant-design-vue/es/...'. Sub-member components are resolved with .then mappings. The initComponentAdapter export and registration pattern remain unchanged; only the component loading strategy is now asynchronous.

Changes

Cohort / File(s) Summary
Async-load ant-design-vue components
docs/src/components/common-ui/vben-form.md
Replaced named imports with defineAsyncComponent for AutoComplete, Button, Checkbox(+Group), DatePicker, Divider, Input(+Password), InputNumber, Mentions, Radio(+Group), RangePicker, Rate, Select, Space, Switch, Textarea, TimePicker, TreeSelect, Upload; switched to 'ant-design-vue/es/...'; retained initComponentAdapter export and component registration, now using async-loaded components.

Sequence Diagram(s)

sequenceDiagram
  participant Form as Form Renderer
  participant Adapter as Component Adapter
  participant Loader as defineAsyncComponent
  participant Lib as ant-design-vue (ES modules)

  Form->>Adapter: request component render
  Adapter->>Loader: resolve component (lazy)
  Loader->>Lib: dynamic import('ant-design-vue/es/...') 
  Lib-->>Loader: module / sub-member
  Loader-->>Adapter: async component
  Adapter-->>Form: render with resolved component
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • mynetfan
  • anncwb
  • jinmao88
  • vince292007

Poem

I nudge the forms with twitches bright,
Swap static bites for loading light—
Hop, hop! Components wake on call,
ES trails through the garden wall.
Async breezes, silky, quick—
Carrots cached, the render slick. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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 coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🔭 Outside diff range comments (4)
docs/src/components/common-ui/vben-form.md (4)

87-89: Missing import for defineAsyncComponent (all async component defs will fail at runtime)

defineAsyncComponent is used but not imported from vue. This will throw at runtime and break the adapter snippet for consumers copying from docs.

Apply this diff to import it:

-import type { Component, SetupContext } from 'vue';
-import { h } from 'vue';
+import type { Component, SetupContext } from 'vue';
+import { defineAsyncComponent, h } from 'vue';

Also applies to: 93-138


188-190: attrs are not merged; they’re passed as a prop (buttons won’t receive attrs like class, style, onClick)

{ ...props, attrs, type: 'default' } sets an attrs prop rather than merging. You want { ...props, ...attrs }.

Apply this diff:

-    DefaultButton: (props, { attrs, slots }) => {
-      return h(Button, { ...props, attrs, type: 'default' }, slots);
-    },
+    DefaultButton: (props, { attrs, slots }) => {
+      return h(Button, { ...props, ...attrs, type: 'default' }, slots);
+    },
@@
-    PrimaryButton: (props, { attrs, slots }) => {
-      return h(Button, { ...props, attrs, type: 'primary' }, slots);
-    },
+    PrimaryButton: (props, { attrs, slots }) => {
+      return h(Button, { ...props, ...attrs, type: 'primary' }, slots);
+    },

Also applies to: 198-200


151-176: Type union terminated early; BaseFormComponentType is currently excluded (TS syntax error)

There’s a stray semicolon after 'IconPicker' which ends the alias before BaseFormComponentType.

Apply this diff:

-  | 'Upload'
-  | 'IconPicker';
-  | BaseFormComponentType;
+  | 'Upload'
+  | 'IconPicker'
+  | BaseFormComponentType;

219-227: notification is used but never imported (runtime ReferenceError)

notification.success is referenced, but there is no import for notification.

Add the import:

+import { notification } from 'ant-design-vue';

Optional: If you want to keep everything lazy-loaded for consistency, you could instead dynamically import it on use:

copyPreferencesSuccess: async (title, content) => {
  const { notification } = await import('ant-design-vue');
  notification.success({
    description: content,
    message: title,
    placement: 'bottomRight',
  });
},
🧹 Nitpick comments (1)
docs/src/components/common-ui/vben-form.md (1)

177-178: async keyword is unnecessary (minor)

initComponentAdapter is marked async but doesn’t await anything.

You can drop async now or keep it if you plan to lazy-load and await in the future.

📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ff4704d and 11dcc71.

📒 Files selected for processing (1)
  • docs/src/components/common-ui/vben-form.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: post-update (windows-latest)
  • GitHub Check: post-update (ubuntu-latest)
  • GitHub Check: Check (windows-latest)
  • GitHub Check: Lint (ubuntu-latest)
  • GitHub Check: Lint (windows-latest)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Check (ubuntu-latest)
🔇 Additional comments (1)
docs/src/components/common-ui/vben-form.md (1)

111-113: Verify sub-member export names from ant-design-vue ESM

You’re resolving sub-exports via .then((res) => res.InputPassword | res.Textarea | res.RadioGroup | res.CheckboxGroup | res.RangePicker). Export names vary across ant-design-vue versions (e.g., Input.Password vs InputPassword, Radio.Group vs RadioGroup). Please confirm these identifiers match the version used by this project to avoid undefined components at runtime.

Would you like me to cross-check the exact ESM export names for your locked ant-design-vue version and propose precise mappings?

Also applies to: 118-123, 128-130

@qianYuanJ qianYuanJ changed the title chore(docs): update the form adapter document docs(vben-form): update the form adapter document Aug 19, 2025
@jinmao88
jinmao88 merged commit 58e3941 into vbenjs:main Aug 19, 2025
dtera pushed a commit to dtera/vue-admin that referenced this pull request Sep 5, 2025
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants