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: form colon support, update docs #5156

Merged
merged 1 commit into from
Dec 16, 2024
Merged

Conversation

mynetfan
Copy link
Collaborator

@mynetfan mynetfan commented Dec 16, 2024

Description

表单支持配置是否在label后显示一个冒号

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

  • New Features

    • Introduced a new property colon to control the display of colons after form labels.
    • Updated form configurations to enforce required fields and enhance label rendering.
  • Documentation

    • Improved clarity and detail in the documentation for the Vben Form component, including property descriptions and validation rules.
  • Bug Fixes

    • Enhanced label rendering logic to conditionally display colons based on the presence of labels.
  • Chores

    • Refined overall structure and readability of the documentation.

@mynetfan mynetfan requested review from anncwb, vince292007 and a team as code owners December 16, 2024 14:28
Copy link

changeset-bot bot commented Dec 16, 2024

⚠️ No Changeset found

Latest commit: ea63172

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 16, 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/form-render/form-field.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

This pull request introduces enhancements to the Vben Form component documentation and implementation. The changes focus on improving form configuration flexibility, particularly by adding a new colon property to control label rendering. The documentation has been updated to provide more explicit descriptions of form properties, validation rules, and component behaviors. The modifications span across documentation, type definitions, and example implementations, aiming to clarify and expand the form component's capabilities.

Changes

File Change Summary
docs/src/components/common-ui/vben-form.md Updated documentation with more detailed descriptions of form properties, validation rules, and component behaviors
packages/@core/ui-kit/form-ui/src/form-render/form-field.vue Added colon prop to conditionally render colon after label text
packages/@core/ui-kit/form-ui/src/form-render/form.vue Integrated colon property into computedSchema
packages/@core/ui-kit/form-ui/src/types.ts Added optional colon property to FormCommonConfig interface
playground/src/views/examples/form/basic.vue Added colon: true to commonConfig and rules: 'required' to username field

Possibly related PRs

Suggested labels

feature

Suggested reviewers

  • vince292007
  • anncwb

Poem

🐰 A form so neat, with colon so sweet
Labels dancing with delight
Validation rules now crystal clear
Configuration taking flight
Vben's magic, rabbit's might! 🌟

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request.


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. (Beta)
  • @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.

@mynetfan mynetfan changed the title feat: form colon support feat: form colon support, update docs Dec 16, 2024
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

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

29-29: Consider adding explicit type definition for the colon prop.

The colon prop would benefit from an explicit boolean type definition with JSDoc comments explaining its purpose.

-  colon,
+  /** Whether to display a colon after the label */
+  colon?: boolean,
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 38805a0 and ea63172.

📒 Files selected for processing (5)
  • docs/src/components/common-ui/vben-form.md (6 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 (1 hunks)
  • playground/src/views/examples/form/basic.vue (2 hunks)
🔇 Additional comments (9)
packages/@core/ui-kit/form-ui/src/form-render/form.vue (2)

89-91: LGTM: Colon property initialization looks good

The colon property is properly initialized with a sensible default value of false and correctly merged from both commonConfig and globalCommonConfig.


114-114: LGTM: Proper property propagation

The colon property is correctly propagated to individual form fields while maintaining the ability to override at the schema level.

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

139-142: LGTM: Well-documented type definition

The colon property is properly typed as an optional boolean with clear JSDoc documentation explaining its purpose.

playground/src/views/examples/form/basic.vue (1)

19-20: LGTM: Clear example implementation

The colon property is properly demonstrated with a helpful comment explaining its purpose.

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

304-307: LGTM! Clean implementation of the colon feature.

The conditional rendering and spacing are well implemented, ensuring the colon only appears when appropriate.

docs/src/components/common-ui/vben-form.md (4)

316-316: LGTM! Clear documentation of the collapsed prop dependency.

The documentation effectively communicates the relationship between collapsed and showCollapseButton props.


319-319: LGTM! Clear explanation of the fieldMappingTime mapping functionality.

The documentation effectively describes how the time range values are mapped to separate fields.


321-323: LGTM! Clear documentation of form submission behavior.

The documentation effectively describes the schema type and form submission triggers.


364-367: LGTM! Well-documented colon property in FormCommonConfig.

The documentation clearly explains the purpose of the colon property for form labels.

playground/src/views/examples/form/basic.vue Show resolved Hide resolved
@mynetfan mynetfan merged commit 593916d into vbenjs:main Dec 16, 2024
15 checks passed
@mynetfan mynetfan deleted the feat/form-colon branch December 16, 2024 14:37
@github-actions github-actions bot locked and limited conversation to collaborators Jan 16, 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.

1 participant