refactor(theme): [ip-address] refactor ip-address theme vars

[zzcr]

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 CSS variable naming conventions for the IP address component, enhancing consistency and clarity.
  • Introduced new variables for improved responsiveness and adaptability across different input sizes.

• Bug Fixes

  • Adjusted expected CSS height values in the test cases for the IP address input box to reflect design updates.

• Documentation

  • Updated method names for better clarity and alignment with the new design framework.

[coderabbitai[bot]]

Walkthrough

The pull request introduces significant updates to the IP address component's CSS styles, focusing on renaming and restructuring CSS variables and mixin calls. The changes include a shift in naming conventions from --ti- to --tv-, adjustments to various component properties, and the introduction of new variables to enhance responsiveness. The updates are reflected in both the index.less and vars.less files, ensuring consistency and alignment with a new design framework.

Changes

Files	Change Summary
packages/theme/src/ip-address/index.less, packages/theme/src/ip-address/vars.less	Updated method calls from .component-css-vars-ip-address() to .inject-IpAddress-vars(), and renamed CSS variables from --ti- to --tv-. Adjusted various properties for consistency and responsiveness.
examples/sites/demos/pc/app/ip-address/size.spec.ts	Modified expected CSS height values for input elements, changing the first input's expected height from '42px' to '40px'.

Possibly related PRs

• #2157: Systematic renaming of CSS custom properties from --ti- to --tv-, aligning with the main PR's changes.
• #2203: Adjustments to font sizes for input components, relevant to the updates in the main PR.
• #2166: Modifications to the IP address component's styles, directly related to the changes in CSS variable definitions.
• #2201: Refactoring of collapse theme variables, involving similar CSS variable naming updates.
• #2202: Refactoring of dialog box theme variables, aligning with the main PR's focus on CSS variable updates.
• #2209: Refactoring of breadcrumb theme variables, transitioning from --ti- to --tv- prefixes, similar to the main PR.

Suggested labels

refactoring

🐰 "In the fields where bunnies play,
CSS changes come our way.
With new names and styles so bright,
Our IP component shines with delight!
Variables fresh, a joyful cheer,
Hop along, the updates are here!" 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b2720621cee8776466b5922960bfcaaa3319219e and 8479aaa759110f86ffa00aa58e1a08c85c107f22.

📒 Files selected for processing (2)

• examples/sites/demos/pc/app/ip-address/size.spec.ts (1 hunks)
• packages/theme/src/ip-address/vars.less (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/theme/src/ip-address/vars.less

🔇 Additional comments (1)

examples/sites/demos/pc/app/ip-address/size.spec.ts (1)

10-10: Verify the updated height and its implications.

The expected height for the first IP address input element has been changed from '42px' to '40px'. This change might reflect an update in the component's design.

Please confirm the following:

1. Is this change intentional and consistent with recent design updates?
2. Are there any other components or tests that might be affected by this height change?
3. Does this change maintain the desired visual hierarchy among the different sizes (40px > 32px > 28px > 24px)?

To help verify the consistency of this change across the codebase, you can run the following script:

This will help identify any other places where the height might need to be updated for consistency.

The test logic itself looks correct, and the change is straightforward. However, it's important to ensure this change is part of a broader, intentional update to the component's design.

✅ Verification successful

Height update from '42px' to '40px' verified and consistent across relevant tests. No issues found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other occurrences of IP address input height specifications
rg --type typescript --type vue '(height|line-height).*?(?:40|42)px' src examples

Length of output: 118

---

Script:

#!/bin/bash
# Search for other occurrences of IP address input height specifications
rg --type ts --type vue '(height|line-height).*?(?:40|42)px' src examples

Length of output: 103

---

Script:

#!/bin/bash
# Search for other occurrences of IP address input height specifications in .ts and .vue files
rg -g "*.ts" -g "*.vue" '(height|line-height).*?(?:40|42)px' src examples

Length of output: 4258

---

Script:

#!/bin/bash
# Search for other occurrences of IP address input height specifications in .ts and .vue files within the examples directory
rg -g "*.ts" -g "*.vue" '(height|line-height).*?(?:40|42)px' examples

Length of output: 4210

---

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.