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

docs: fix typos #5105

Merged
merged 1 commit into from
Dec 11, 2024
Merged

docs: fix typos #5105

merged 1 commit into from
Dec 11, 2024

Conversation

mynetfan
Copy link
Collaborator

@mynetfan mynetfan commented Dec 11, 2024

Description

修复文档错字;补全formhandleValuesChange属性

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

  • Documentation

    • Updated Vben Form documentation with new examples for integration with Ant Design Vue.
    • Expanded API section for the useVbenForm hook, detailing methods and properties.
    • Improved clarity and structure of Vben Modal documentation, including updated descriptions and API details.
  • New Features

    • Introduced handleValuesChange property in the useVbenForm props.
    • Added initComponentAdapter method to Vben Form documentation.
  • Bug Fixes

    • Clarified internationalization and theme color issues in Vben Modal documentation.

@mynetfan mynetfan requested review from anncwb, vince292007 and a team as code owners December 11, 2024 06:37
Copy link

changeset-bot bot commented Dec 11, 2024

⚠️ No Changeset found

Latest commit: 079f4b5

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 11, 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/vben-use-form.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)

Walkthrough

The pull request includes significant updates to the documentation for the Vben Form and Vben Modal components, enhancing clarity and usability. Key additions include detailed examples for integrating with Ant Design Vue, an expanded API section, and new properties such as handleValuesChange. Additionally, modifications to the vben-use-form.vue component simplify the handling of form value changes. The overall structure of the documentation has been refined to improve navigation and comprehension.

Changes

File Path Change Summary
docs/src/components/common-ui/vben-form.md Updated documentation with additional details on using Ant Design Vue, expanded adapters section, new code snippets, added handleValuesChange property, introduced initComponentAdapter method, and refined structure.
docs/src/components/common-ui/vben-modal.md Improved clarity in the introductory section, clarified internationalization issues, rephrased modal feature descriptions, expanded connectedComponent explanation, and updated API section for better navigation.
packages/@core/ui-kit/form-ui/src/vben-use-form.vue Updated watch function in vben-use-form.vue to simplify handling of form value changes, directly invoking handleValuesChange, while maintaining debounce functionality. Interface context updated for clarity.

Possibly related PRs

Suggested labels

documentation

Suggested reviewers

  • vince292007
  • anncwb

Poem

🐰 In the garden of forms, we play,
With Ant Design Vue, bright as day.
New props and snippets, oh what a sight,
Handling values, everything feels right!
Documentation blooms, clear and bright,
Hop along, dear friends, to the coding delight! 🌼


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: 0

🧹 Outside diff range and nitpick comments (3)
docs/src/components/common-ui/vben-modal.md (1)

114-114: LGTM! Consider adding a code example.

The explanation of appendToMain property is clear, accurate, and provides valuable implementation details. To further enhance the documentation, consider adding a minimal code example demonstrating the correct usage with the Page component's auto-content-height property.

Example addition:

 `appendToMain`可以指定将弹窗挂载到内容区域,打开这种弹窗时,内容区域以外的部分(标签栏、导航菜单等等)不会被遮挡。默认情况下,弹窗会挂载到body上。但是:挂载到内容区域时,作为页面根容器的`Page`组件,需要设置`auto-content-height`属性,以便弹窗能够正确计算高度。
+
+```vue
+<template>
+  <Page auto-content-height>
+    <VbenModal :append-to-main="true">
+      <!-- Modal content -->
+    </VbenModal>
+  </Page>
+</template>
+```
packages/@core/ui-kit/form-ui/src/vben-use-form.vue (1)

65-67: Consider adding error handling for the form value changes.

The simplified implementation looks good, but consider adding error handling for the handleValuesChange callback to gracefully handle any potential errors during form value updates.

-    forward.value.handleValuesChange?.(toRaw(form.values));
+    try {
+      forward.value.handleValuesChange?.(toRaw(form.values));
+    } catch (error) {
+      console.error('Error handling form value changes:', error);
+    }
docs/src/components/common-ui/vben-form.md (1)

309-309: Add usage example for handleValuesChange.

The property documentation is clear, but it would be helpful to add a code example demonstrating its usage, especially for form value change monitoring scenarios.

Consider adding an example like:

const [Form, formApi] = useVbenForm({
  handleValuesChange: (values) => {
    console.log('Form values changed:', values);
    // Perform additional actions with the updated values
  },
});
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4a20156 and 079f4b5.

📒 Files selected for processing (3)
  • docs/src/components/common-ui/vben-form.md (1 hunks)
  • docs/src/components/common-ui/vben-modal.md (1 hunks)
  • packages/@core/ui-kit/form-ui/src/vben-use-form.vue (1 hunks)

@mynetfan mynetfan merged commit 43adc94 into vbenjs:main Dec 11, 2024
14 checks passed
@mynetfan mynetfan deleted the docs/fix-typos branch December 11, 2024 06:48
@anncwb anncwb added the documentation Improvements or additions to documentation label Dec 12, 2024
@coderabbitai coderabbitai bot mentioned this pull request Dec 16, 2024
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants