fix: the focus style and antd of the input box validation failure should be consistent

[imdap]

Description

表单输入框校验失败的focus样式和antd保持一致

before:

after: 与antd样式保持一致

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

  • Enhanced visual feedback for form fields in invalid state with added focus shadow effect.

• Bug Fixes

  • Improved styling for better user experience when interacting with form fields.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f197139

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 enhance the form-field.vue component by modifying the class binding associated with its styling. The update specifically focuses on improving visual feedback for the component when it is in an invalid state, adding a focus shadow effect to indicate the field's status more clearly.

Changes

File Path	Change Summary
packages/@core/ui-kit/form-ui/src/form-render/form-field.vue	Modified class binding to enhance styling for invalid state, adding a focus shadow effect.

Possibly related PRs

• fix: hover border style same as antd style when validate error #4409: This PR modifies the form-field.vue file to enhance the visual feedback for invalid states by adding a hover border style.
• fix: missing the default required label style for components such as select #4444: This PR alters the form-field.vue file, changing the logic for determining required fields, which may relate to overall user experience improvements in form validation.

Suggested labels

enhancement

Poem

🐇 In the meadow where fields bloom bright,
A shadow dances, a charming sight.
With every focus, the colors play,
Invalid states now fade away.
A hop, a skip, a joyful cheer,
For clearer forms, we hold so dear! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b12ff2d and f197139.

Files selected for processing (1)

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

Additional comments not posted (1)

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

267-269: Approve the enhanced invalid field styling.

The changes to the class binding expression improve the visual feedback for invalid form fields:

• The destructive border color effectively communicates the error state.
• The focus and hover styles provide additional emphasis on the invalid field.
• The custom focus shadow adds a subtle visual cue when the invalid field is focused.

The use of a low opacity for the focus shadow is a good choice to ensure it doesn't overpower the destructive border.

Suggestions:

• Consider extracting the rgba color to a variable or constant for better maintainability and reusability.
• Ensure that the destructive color meets accessibility contrast ratios against the field's background color.

Overall, the changes enhance the user experience by providing clear visual indicators for invalid form fields.

---

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.