fix(form): [form] fix form tooltip class name

[gimmyhehe]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Updated the package to version 3.18.1, now including an MIT license.
  • Added new development dependencies to enhance testing capabilities.

• Bug Fixes

  • Corrected a typographical error in validation comments for improved clarity.

• Refactor

  • Improved CSS class management for better readability while maintaining functionality.

[coderabbitai]

Walkthrough

The pull request updates the @opentiny/vue-form-item package, changing its version from 3.18.0 to 3.18.1. It adds a license field, modifies the dependencies section, and restructures the devDependencies. Additionally, minor adjustments in the pc.vue file enhance validation handling and CSS class management. These changes aim to improve the package's metadata organization and code clarity without affecting core functionalities.

Changes

File Path	Change Summary
packages/vue/src/form-item/package.json	Updated version to 3.18.1, added license field, restructured devDependencies, modified dependencies.
packages/vue/src/form-item/src/pc.vue	Minor modifications for validation handling and CSS class management, including typo correction and improved readability.

Possibly related PRs

• feat(form): [form] x-design theme refresh #2093: This PR modifies the error-slot.vue component to enhance error message display, which may relate to the changes in pc.vue regarding validation handling and CSS class management.
• docs(form): [form] demo fix to adapter x-design #2113: This PR includes changes to the error-slot.vue component's styling, specifically the custom-error class, which connects to the modifications in pc.vue that also involve CSS class management.

Suggested labels

enhancement

Suggested reviewers

• zzcr

🐰 In the garden, changes bloom,
A license added, dispelling gloom.
Classes refined, a clearer sight,
In code we hop, with pure delight!
Version's new, our joy takes flight! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fde4fab and 78350f1.

Files selected for processing (2)

• packages/vue/src/form-item/package.json (1 hunks)
• packages/vue/src/form-item/src/pc.vue (2 hunks)

Files skipped from review due to trivial changes (1)

• packages/vue/src/form-item/src/pc.vue

Additional comments not posted (3)

packages/vue/src/form-item/package.json (3)

4-4: LGTM!

The version update to 3.18.1, the addition of the "MIT" license, and the restructuring of the devDependencies section with new entries are informational changes that do not affect the package's functionality. The changes to the development and testing setup should not impact the package's runtime behavior.

Also applies to: 6-6, 20-23

---

18-18: LGTM!

The reordering of @opentiny/vue-tooltip in the dependencies section is a non-functional change that does not affect the package's behavior.

---

16-16: Verify the impact of the new @opentiny/vue-icon dependency.

The inclusion of @opentiny/vue-icon in the dependencies section suggests that the package now relies on the icon package. This could introduce new features or UI elements.

Please ensure that the new dependency is properly integrated and does not cause any unintended changes to the package's functionality or UI.

Verification successful

---

Verified: @opentiny/vue-icon dependency is properly integrated and widely used.

The @opentiny/vue-icon package is extensively used throughout the project, providing icons for various components such as buttons, alerts, dropdowns, and more. Its inclusion as a dependency appears to be intentional and necessary for maintaining a consistent and functional user interface across the application.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage and impact of the new `@opentiny/vue-icon` dependency.

# Test: Search for the import and usage of the `@opentiny/vue-icon` package.
rg --type typescript -A 5 $'@opentiny/vue-icon'

# Test: Search for any new or modified UI elements related to icons.
fd --type file --extension vue --exec rg --type vue -A 5 $'<icon'

Length of output: 129032

---

Script:

#!/bin/bash
# Description: Verify the usage and impact of the new `@opentiny/vue-icon` dependency.

# Search for imports or usage of @opentiny/vue-icon
echo "Searching for @opentiny/vue-icon usage:"
grep -r "@opentiny/vue-icon" .

# Search for icon-related elements in .vue files
echo "Searching for icon-related elements in .vue files:"
find . -name "*.vue" -exec grep -H "<icon" {} +

# Check recent changes related to icons or the new dependency
echo "Recent changes related to icons or @opentiny/vue-icon:"
git log -n 10 --grep="icon" --grep="@opentiny/vue-icon" --pretty=format:"%h - %s" --author-date-order

Length of output: 149789

---

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.