Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(tag): update tag's padding,border-radius #2458

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

shenjunjian
Copy link
Collaborator

@shenjunjian shenjunjian commented Oct 29, 2024

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
    • Enhanced styling for the Tag component, including updated font sizes, padding, and border radii for mini, small, and medium tags.
  • Bug Fixes
    • Corrected inconsistencies in padding and border radius values to improve visual alignment across different tag sizes.

Copy link

coderabbitai bot commented Oct 29, 2024

Walkthrough

The changes in this pull request involve multiple updates to the LESS variables for the Tag component's styling. Adjustments include modifications to font sizes, padding values, and border radii for various tag sizes (mini, small, medium). The changes reflect a transition from variable references to fixed values for certain properties, along with overall adjustments in sizing and spacing across different tag states.

Changes

File Change Summary
packages/theme/src/tag/vars.less Updated LESS variables for the Tag component:
- Mini tag: font size, horizontal/vertical padding adjustments.
- Small tag: padding and border radius changes.
- Default tag: padding and border radius updates.
- Medium tag: font size comment added, padding, and icon size adjustments.

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • zzcr

🐰 In the garden where tags bloom bright,
Adjustments made to bring delight.
From padding small to borders wide,
Each little change, a joyful stride!
With colors fresh and sizes neat,
Our tags now dance, a lovely feat! 🌼


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
🪧 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.

@github-actions github-actions bot added the bug Something isn't working label Oct 29, 2024
Copy link

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (5)
packages/theme/src/tag/vars.less (5)

23-27: Consider maintaining design system consistency for padding values.

While using var(--tv-font-size-sm) improves design system consistency, switching from design system variables to fixed padding values (3px) might break this consistency. Consider using design system spacing variables instead.

- --tv-Tag-padding-x-mini: 3px;
+ --tv-Tag-padding-x-mini: var(--tv-space-2xs);

38-42: Border radius change improves visual hierarchy, but consider system spacing.

The border-radius change from xs to sm improves the visual hierarchy. However, like the mini tag, consider using design system spacing variables for padding values instead of fixed pixels.

- --tv-Tag-padding-x-small: 7px;
+ --tv-Tag-padding-x-small: var(--tv-space-xs);

62-62: Remove redundant inline comment.

The comment "//14" is redundant and could become outdated if the --tv-font-size-md variable changes. Consider removing it or documenting it properly.

- --tv-Tag-font-size-medium: var(--tv-font-size-md); //14
+ --tv-Tag-font-size-medium: var(--tv-font-size-md);

70-72: Icon size reduction improves visual balance.

The reduction of icon size from 20px to 16px improves the visual proportions. However, consider using design system spacing variables for the icon padding.

- --tv-Tag-only-icon-padding-medium: 7px;
+ --tv-Tag-only-icon-padding-medium: var(--tv-space-xs);

Line range hint 18-72: Consider maintaining design system consistency across all size variants.

There's a pattern of moving from design system variables to fixed pixel values across all tag sizes. While the specific values might meet current requirements, this approach could lead to:

  1. Inconsistency with other components
  2. Harder maintenance when design system spacing needs to change
  3. Potential issues with different screen densities

Consider creating new design system spacing variables if the current ones don't meet the tag component's needs, rather than using fixed values.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between fd535ac and c90c4f9.

📒 Files selected for processing (1)
  • packages/theme/src/tag/vars.less (2 hunks)

Comment on lines +51 to +55
--tv-Tag-padding-x: 11px;
// 默认标签垂直间距
--tv-Tag-padding-y: 0.5px;
--tv-Tag-padding-y: 2.5px;
// 默认标签圆角
--tv-Tag-border-radius: var(--tv-border-radius-sm);
--tv-Tag-border-radius: var(--tv-border-radius-md);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Avoid fractional pixel values for cross-browser consistency.

The 2.5px padding might render inconsistently across browsers. Consider rounding to whole pixels and using design system spacing variables.

- --tv-Tag-padding-y: 2.5px;
+ --tv-Tag-padding-y: 3px; /* or var(--tv-space-2xs) */
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
--tv-Tag-padding-x: 11px;
// 默认标签垂直间距
--tv-Tag-padding-y: 0.5px;
--tv-Tag-padding-y: 2.5px;
// 默认标签圆角
--tv-Tag-border-radius: var(--tv-border-radius-sm);
--tv-Tag-border-radius: var(--tv-border-radius-md);
--tv-Tag-padding-x: 11px;
// 默认标签垂直间距
--tv-Tag-padding-y: 3px;
// 默认标签圆角
--tv-Tag-border-radius: var(--tv-border-radius-md);

@zzcr zzcr merged commit f4ca536 into opentiny:release-3.19.0 Oct 29, 2024
7 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Oct 29, 2024
13 tasks
@shenjunjian shenjunjian deleted the fix-tag-size branch November 7, 2024 01:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants