feat(tag-group): [tag-group] updata ttag-group xdesign

[wuyiping0628]

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

  • Default size for tags changed from 'medium' to 'small', enhancing the user interface by promoting a more compact design.
  • Simplified tag data structures across various components, improving consistency in tag representation.

• Bug Fixes

  • Adjusted text labels for tag sizes to improve clarity and consistency in the user interface.

• Style

  • Enhanced visual distinction of tags with updated border styles and padding adjustments for different tag sizes.

• Documentation

  • Updated documentation to reflect changes in default tag sizes and their implications for user experience.

[coderabbitai]

Walkthrough

The pull request introduces several changes primarily focused on modifying the default size property of tag components from 'medium' to 'small'. This adjustment is reflected across multiple files, including JavaScript and Vue components, as well as related documentation and styling files. Additionally, the data structures for tag representations have been simplified, consolidating various tag entries into a more uniform format. These updates aim to enhance consistency in the tag component's appearance and behavior.

Changes

Files	Change Summary
examples/sites/demos/apis/tag-group.js	Changed default size property from 'medium' to 'small'.
examples/sites/demos/pc/app/tag-group/basic-usage-composition-api.vue	Simplified tag data structure, reducing distinct tag entries from nine to five.
examples/sites/demos/pc/app/tag-group/basic-usage.vue	Condensed tag data structure with generic naming for tags, maintaining type distinctions.
examples/sites/demos/pc/app/tag-group/tag-group-effect-composition-api.vue	Adjusted whitespace and standardized tag names in the items array.
examples/sites/demos/pc/app/tag-group/tag-group-effect.vue	Removed extra spaces in tag labels and simplified the items array.
examples/sites/demos/pc/app/tag-group/tag-group-size-composition-api.vue	Updated text labels for tag sizes and simplified the items array to a more generic format.
examples/sites/demos/pc/app/tag-group/tag-group-size.vue	Changed text labels for tag sizes and consolidated tag entries in the items array.
examples/sites/demos/pc/app/tag-group/webdoc/tag-group.js	Updated documentation to reflect the new default size of the tag group component.
packages/theme/src/tag/index.less	Added border styles and adjusted padding and font sizes for tag states.
packages/theme/src/tag/vars.less	Updated styling variables for tag sizes and themes, specifying pixel values and color definitions.
packages/vue/src/tag-group/src/index.ts	Modified default value of size property in tagGroupProps from 'medium' to 'small'.

Suggested labels

documentation

Poem

🐇 In the garden where tags bloom bright,
A shift in size brings pure delight.
From medium to small, they now do play,
Simplified names brighten the day.
With borders and colors, they dance in cheer,
A tag's new journey, we hold dear! 🌼

Tip

OpenAI O1 model for chat

• We have deployed OpenAI's latest O1 model for chat.
• OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model.
• Please share any feedback with us in the discussions post.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 088ab18 and 985244d.

Files selected for processing (3)

• examples/sites/demos/pc/app/tag-group/basic-usage.spec.js (1 hunks)
• examples/sites/demos/pc/app/tag-group/tag-group-effect.spec.js (1 hunks)
• examples/sites/demos/pc/app/tag-group/tag-group-size.spec.js (1 hunks)

Additional comments not posted (22)

examples/sites/demos/pc/app/tag-group/tag-group-size.spec.js (3)

8-9: LGTM!

The test case has been correctly updated to reflect the new expected height and line-height values for medium-sized tags.

---

12-13: LGTM!

The test case has been correctly updated to reflect the new expected height and line-height values for small-sized tags.

---

16-17: LGTM!

The test case has been correctly updated to reflect the new expected height and line-height values for mini-sized tags.

examples/sites/demos/pc/app/tag-group/basic-usage.spec.js (5)

9-11: LGTM!

The changes to the background color and text color expectations for the first tag are valid and align with the updated styling mentioned in the AI-generated summary. The use of a generic selector and .nth(0) to retrieve the tag is a good practice for maintainability.

---

13-15: LGTM!

The changes to the background color and text color expectations for the second tag are valid and align with the updated styling mentioned in the AI-generated summary. The use of a generic selector and .nth(1) to retrieve the tag is a good practice for maintainability.

---

17-19: LGTM!

The changes to the background color and text color expectations for the third tag are valid and align with the updated styling mentioned in the AI-generated summary. The use of a generic selector and .nth(2) to retrieve the tag is a good practice for maintainability.

---

21-23: LGTM!

The changes to the background color and text color expectations for the fourth tag are valid and align with the updated styling mentioned in the AI-generated summary. The use of a generic selector and .nth(3) to retrieve the tag is a good practice for maintainability.

---

25-27: LGTM!

The changes to the background color and text color expectations for the fifth tag are valid and align with the updated styling mentioned in the AI-generated summary. The use of a generic selector and .nth(4) to retrieve the tag is a good practice for maintainability.

examples/sites/demos/pc/app/tag-group/tag-group-effect.spec.js (14)

9-10: LGTM!

The changes simplify the code by directly accessing the specific dark tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the dark tag.

---

13-14: LGTM!

The changes simplify the code by directly accessing the specific dark tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the dark tag.

---

17-18: LGTM!

The changes simplify the code by directly accessing the specific dark tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the dark tag.

---

21-22: LGTM!

The changes simplify the code by directly accessing the specific dark tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the dark tag.

---

25-26: LGTM!

The changes simplify the code by directly accessing the specific dark tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the dark tag.

---

29-31: LGTM!

The changes simplify the code by directly accessing the specific light tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the light tag.

---

33-35: LGTM!

The changes simplify the code by directly accessing the specific light tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the light tag.

---

37-39: LGTM!

The changes simplify the code by directly accessing the specific light tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the light tag.

---

41-43: LGTM!

The changes simplify the code by directly accessing the specific light tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the light tag.

---

45-47: LGTM!

The changes simplify the code by directly accessing the specific light tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the light tag.

---

49-51: LGTM!

The changes simplify the code by directly accessing the specific plain tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the plain tag.

---

53-55: LGTM!

The changes simplify the code by directly accessing the specific plain tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the plain tag.

---

57-59: LGTM!

The changes simplify the code by directly accessing the specific plain tag based on its order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the plain tag.

---

61-67: LGTM!

The changes simplify the code by directly accessing the specific plain tags based on their order using the getByText method and the nth selector. The expected CSS properties align with the new styling of the plain tags.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

[zzcr]

这里的修改需要评估下对saas主题的影响