Skip to content
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

feat: add submitOnChange props to vben form #5032

Merged
merged 1 commit into from
Dec 5, 2024

Conversation

DesignHhuang
Copy link
Contributor

@DesignHhuang DesignHhuang commented Dec 5, 2024

Description

在vben form 中添加 submitOnChange 属性用以控制是否在字段改变时提交查询。close: #5031

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Summary by CodeRabbit

  • New Features

    • Introduced a submitOnChange property for forms, allowing automatic submission when field values change.
    • Enhanced documentation for the Vben Form component, including clearer examples and a new section on adapters for various UI frameworks.
  • Bug Fixes

    • Improved clarity and usability of the form documentation to facilitate better understanding of configuration and usage.
  • Documentation

    • Updated documentation to include detailed explanations of new properties and methods related to form behavior and validation.

@DesignHhuang DesignHhuang requested review from anncwb, vince292007 and a team as code owners December 5, 2024 02:51
Copy link

changeset-bot bot commented Dec 5, 2024

⚠️ No Changeset found

Latest commit: bcbe81a

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

Copy link
Contributor

coderabbitai bot commented Dec 5, 2024

Walkthrough

The pull request introduces the submitOnChange property to the Vben Form component, enhancing its configuration options. This property allows forms to submit automatically upon field value changes. Documentation has been updated to reflect these changes, including detailed explanations and examples for using the new property across various UI frameworks. The implementation spans multiple files, including updates to the form API, component props, and Vue components, ensuring consistent behavior and improved usability.

Changes

File Path Change Summary
docs/src/components/common-ui/vben-form.md Updated documentation to include submitOnChange property, usage examples, and adapter details.
docs/src/demos/vben-vxe-table/form/index.vue Added submitOnChange: false to formOptions object for form configuration.
packages/@core/ui-kit/form-ui/src/form-api.ts Introduced submitOnChange property in VbenFormProps interface, initialized to false.
packages/@core/ui-kit/form-ui/src/types.ts Added optional submitOnChange property to VbenFormProps interface.
packages/@core/ui-kit/form-ui/src/vben-use-form.vue Implemented a watcher for form.values to trigger submission based on submitOnChange.
playground/src/views/examples/vxe-table/form.vue Added submitOnChange: true to formOptions object for automatic submission on field changes.

Assessment against linked issues

Objective Addressed Explanation
Add submitOnChange property to form component (#5031)
Enable automatic form submission on field change (#5031)

Possibly related PRs

Suggested labels

feature

Suggested reviewers

  • vince292007
  • anncwb

Poem

In fields of code, we hop and play,
A new submitOnChange brightens the day.
With forms that dance at every tweak,
Our user joy is what we seek! 🐇✨
So let the values change and flow,
A seamless form, watch it glow!

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.

docs/src/demos/vben-vxe-table/form/index.vue

Oops! Something went wrong! :(

ESLint: 9.16.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/node_modules/@vben/eslint-config/dist/index.mjs' imported from /eslint.config.mjs
at finalizeResolution (node:internal/modules/esm/resolve:257:11)
at moduleResolve (node:internal/modules/esm/resolve:914:10)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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

Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (3)
packages/@core/ui-kit/form-ui/src/vben-use-form.vue (1)

62-68: Consider making debounce time configurable and adding error handling

While the implementation is solid, consider these improvements:

  1. Make the debounce time configurable through props to support different use cases
  2. Add error handling for the submission callback

Consider this enhancement:

 interface Props extends VbenFormProps {
   formApi: ExtendedFormApi;
+  submitDebounceMs?: number;
 }

 watch(
   () => form.values,
   useDebounceFn(() => {
-    state.value.submitOnChange && props.formApi?.submitForm();
+    if (!state.value.submitOnChange) return;
+    try {
+      props.formApi?.submitForm();
+    } catch (error) {
+      console.error('Auto-submission failed:', error);
+    }
-  }, 300),
+  }, props.submitDebounceMs ?? 300),
   { deep: true },
 );
packages/@core/ui-kit/form-ui/src/types.ts (1)

345-349: LGTM! Consider enhancing documentation.

The submitOnChange property is well-defined with appropriate type and documentation.

Consider adding examples in the JSDoc comment to illustrate common use cases, such as:

 /**
  * 是否在字段值改变时提交表单
  * @default false
+ * @example
+ * // Auto-submit on field changes
+ * submitOnChange: true
+ * 
+ * // Manual submit only (default)
+ * submitOnChange: false
  */
docs/src/components/common-ui/vben-form.md (1)

319-319: Enhance documentation with usage examples.

The submitOnChange property is well-documented in the Props table, but could benefit from additional examples.

Consider adding a dedicated example section showing:

  1. Basic usage with auto-submission
  2. Integration with form validation
  3. Performance considerations with debouncing

Example addition:

| submitOnChange | 字段值改变时提交表单 | `boolean` | false |
+
+### 自动提交示例
+
+```vue
+<script setup lang="ts">
+import { useVbenForm } from '#/adapter/form';
+
+const [Form, formApi] = useVbenForm({
+  submitOnChange: true,
+  handleSubmit: async (values) => {
+    console.log('Form submitted with values:', values);
+  }
+});
+</script>
+```
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7ab0025 and bcbe81a.

📒 Files selected for processing (6)
  • docs/src/components/common-ui/vben-form.md (1 hunks)
  • docs/src/demos/vben-vxe-table/form/index.vue (1 hunks)
  • packages/@core/ui-kit/form-ui/src/form-api.ts (1 hunks)
  • packages/@core/ui-kit/form-ui/src/types.ts (1 hunks)
  • packages/@core/ui-kit/form-ui/src/vben-use-form.vue (2 hunks)
  • playground/src/views/examples/vxe-table/form.vue (1 hunks)
🔇 Additional comments (4)
playground/src/views/examples/vxe-table/form.vue (1)

68-69: LGTM! Clear example implementation of submitOnChange

The implementation correctly demonstrates the new submitOnChange feature with proper documentation.

docs/src/demos/vben-vxe-table/form/index.vue (1)

79-80: LGTM! Good documentation example with default behavior

The implementation correctly shows the default behavior with submitOnChange: false, providing a good contrast to the playground example.

packages/@core/ui-kit/form-ui/src/vben-use-form.vue (1)

9-11: LGTM! Clean import organization

The imports are well-organized, separating Vue core, utility functions, and component imports.

packages/@core/ui-kit/form-ui/src/form-api.ts (1)

39-39: LGTM! Default state properly initialized.

The submitOnChange property is correctly initialized to false in the default state, matching the interface definition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FEATURE: 在form 表单中新增 submitOnChange 属性
2 participants