fix: some antd components failed to verify styles

[imdap]

Description

一些antd组件在校验失败后的边框样式

before:

after:

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 password input field in the form configuration, enhancing user input options.

• Style

  • Updated styles for form validation error states across various input components, improving visual feedback during user interactions.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c47786

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]

Walkthrough

The changes in this pull request focus on enhancing the form validation experience within the Ant Design framework. CSS styles for various input components have been updated to provide clearer visual feedback for error states. Additionally, a new password input field has been introduced in the form configuration, expanding its functionality and ensuring that user input is validated effectively.

Changes

File Path	Change Summary
packages/styles/src/antd/index.css	Updated CSS styles for form validation error states across Select, Input Number, Password, and Picker components.
playground/src/views/examples/form/rules.vue	Added a new password input field with validation rules to the form configuration.

Possibly related PRs

• perf: display border status color when the form is verified incorrectly #4407: Enhances visual feedback for form validation by modifying border colors for components.
• feat: default form validation rules applicable to selector components #4442: Introduces default validation rules for selector components, aligning with form validation styles.
• fix: missing the default required label style for components such as select #4444: Addresses the default required label style for select components, relevant to validation updates.
• fix: the focus style and antd of the input box validation failure should be consistent #4446: Modifies focus style for input boxes during validation failures, relating to error state changes.
• fix: form verification style fails in pop-up window #4452: Fixes validation styles for Ant Design components in modals, connecting to updates on form validation states.

Suggested labels

bug

Suggested reviewers

• vince292007
• anncwb

🐰 In the garden, where forms do play,
New styles bloom in a vibrant array.
With passwords tucked in, validation's bright,
Errors now dance in a clearer light.
A hop and a skip, all inputs align,
In the world of forms, everything's fine! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 81a9acc and 7c47786.

Files selected for processing (2)

• packages/styles/src/antd/index.css (1 hunks)
• playground/src/views/examples/form/rules.vue (1 hunks)

Additional comments not posted (6)

packages/styles/src/antd/index.css (5)

15-22: LGTM!

The styles for the select component in the error state are implemented correctly. The border color and box shadow effects provide clear visual feedback to the user when the form is in an error state.

---

24-27: LGTM!

The style for the input number component in the error state is implemented correctly. The box shadow effect provides clear visual feedback to the user when the form is in an error state.

---

29-33: LGTM!

The styles for the password input component in the error state are implemented correctly. The border color and box shadow effects provide clear visual feedback to the user when the form is in an error state.

---

35-38: LGTM!

The style for the picker component's active bar in the error state is implemented correctly. The background color provides clear visual feedback to the user when the form is in an error state.

---

40-42: LGTM!

The style for the picker component in the error state is implemented correctly. The box shadow effect provides clear visual feedback to the user when the form is in an error state.

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

169-177: LGTM!

The addition of the password field using the InputPassword component is a good choice for handling sensitive information securely. The field configuration, including the placeholder, field name, label, and required validation, is clear and aligns with common form design practices.

This change expands the form's functionality as intended in the PR objectives while ensuring that the password is a mandatory input for form submission.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.