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

fix: form support disabledOnInputListener #5127

Merged
merged 2 commits into from
Dec 13, 2024

Conversation

mynetfan
Copy link
Collaborator

@mynetfan mynetfan commented Dec 13, 2024

Description

修复ElementPlus组件库Select等组件的onInput会导致表单值意外改变的问题。
fix: #5122
fix: #5090

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

Release Notes

  • New Features

    • Introduced a disabledOnInputListener option for enhanced control over input event handling in forms.
    • Added a filterable option to the Select component, allowing users to filter options.
  • Bug Fixes

    • Improved validation rules for form fields, ensuring accurate error messaging for required fields.
  • Documentation

    • Updated interfaces to include the new disabledOnInputListener property for better configuration clarity.

@mynetfan mynetfan requested review from anncwb, vince292007 and a team as code owners December 13, 2024 03:02
Copy link

changeset-bot bot commented Dec 13, 2024

⚠️ No Changeset found

Latest commit: 519086f

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 13, 2024

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.

packages/@core/ui-kit/form-ui/src/types.ts

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)

Walkthrough

The changes in this pull request introduce a new configuration option, disabledOnInputListener, to enhance form input handling in the Vben Admin framework. This property is added to various components and interfaces, allowing for the disabling of input event listeners on form fields. Additionally, the Select component in the demo form is modified to include a filterable property, enabling option filtering. The overall structure and validation rules of the forms remain intact while improving configurability and addressing specific bugs related to input handling.

Changes

File Path Change Summary
apps/web-ele/src/adapter/form.ts Added disabledOnInputListener property to setupVbenForm configuration for input event control.
apps/web-ele/src/views/demos/form/basic.vue Updated Select component componentProps to include filterable: true for option filtering.
packages/@core/ui-kit/form-ui/src/config.ts Included disabledOnInputListener in the configuration object for setupVbenForm.
packages/@core/ui-kit/form-ui/src/form-render/form-field.vue Added disabledOnInputListener to Props interface and modified fieldBindEvent logic.
packages/@core/ui-kit/form-ui/src/form-render/form.vue Added disabledOnInputListener to commonConfig and globalCommonConfig in computedSchema.
packages/@core/ui-kit/form-ui/src/types.ts Added disabledOnInputListener to FormCommonConfig and VbenFormAdapterOptions interfaces.

Assessment against linked issues

Objective Addressed Explanation
Address bug with filtering in Select component (#5122)
Fix issue with invalid prop type for Select component (#5090)

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • anncwb
  • vince292007

🐰 "In the fields where rabbits play,
New changes hop in every day.
With filters added, forms delight,
Input listeners now take flight!
Let's celebrate this joyful tune,
For forms are better, oh so soon!" 🐇


📜 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 9418cbf and 519086f.

📒 Files selected for processing (1)
  • packages/@core/ui-kit/form-ui/src/types.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/@core/ui-kit/form-ui/src/types.ts

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 generate docstrings to generate docstrings for this PR. (Experiment)
  • @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 (2)
packages/@core/ui-kit/form-ui/src/form-render/form.vue (1)

93-93: LGTM! Consider adding JSDoc comments.

The addition of disabledOnInputListener is well-integrated into the existing configuration structure. This change aligns with the PR's objective to prevent unintended form value changes.

Consider adding JSDoc comments to document the purpose and default value of this property, similar to other properties in the configuration:

+/**
+ * Whether to disable input event listeners for form fields
+ * @default false
+ */
 disabledOnInputListener = false,

Also applies to: 115-115

packages/@core/ui-kit/form-ui/src/form-render/form-field.vue (1)

231-238: Simplify the conditional event binding logic.

The current implementation has some redundancy in handling the disabledOnInputListener condition. The code can be simplified while maintaining the same functionality.

Consider this more concise implementation:

-  return disabledOnInputListener
-    ? {
-        onInput: undefined,
-      }
-    : {};
+  return disabledOnInputListener ? { onInput: undefined } : {};
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1d3729a and 9418cbf.

📒 Files selected for processing (6)
  • apps/web-ele/src/adapter/form.ts (1 hunks)
  • apps/web-ele/src/views/demos/form/basic.vue (1 hunks)
  • packages/@core/ui-kit/form-ui/src/config.ts (1 hunks)
  • packages/@core/ui-kit/form-ui/src/form-render/form-field.vue (2 hunks)
  • packages/@core/ui-kit/form-ui/src/form-render/form.vue (2 hunks)
  • packages/@core/ui-kit/form-ui/src/types.ts (2 hunks)
🔇 Additional comments (4)
apps/web-ele/src/adapter/form.ts (1)

17-18: LGTM! Clear solution for preventing unintended form updates.

The addition of disabledOnInputListener effectively prevents unintended form value updates from input events in components like Select. The Chinese comment clearly explains the rationale.

packages/@core/ui-kit/form-ui/src/config.ts (2)

47-51: LGTM! Clean implementation with backward compatibility.

The disabledOnInputListener config is properly integrated with the existing configuration system, maintaining backward compatibility with its default false value.


54-56: LGTM! Proper config propagation.

The config is correctly propagated to DEFAULT_FORM_COMMON_CONFIG, following the established pattern.

apps/web-ele/src/views/demos/form/basic.vue (1)

142-142: LGTM! Enhanced Select component with filtering support.

Adding filterable: true to the Select component improves user experience by enabling option filtering. This change works in conjunction with the new disabledOnInputListener to prevent unintended form updates during filtering.

packages/@core/ui-kit/form-ui/src/types.ts Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant