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(base-select): fix size style #2541

Merged
merged 1 commit into from
Nov 22, 2024
Merged

Conversation

kagol
Copy link
Member

@kagol kagol commented Nov 22, 2024

PR

主要更新:将写死的多选tag高度动态计算,以适配多种主题。

新老主题效果对比:

image

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

@kagol kagol added the bug Something isn't working label Nov 22, 2024
Copy link

coderabbitai bot commented Nov 22, 2024

Walkthrough

The changes involve updates to the base-select component's styling in two files: index.less and vars.less. The index.less file has had fixed pixel heights for tag elements replaced with CSS variables to improve flexibility. The vars.less file introduces new CSS custom properties for different tag sizes, calculated based on existing dimensions. The modifications enhance the organization of styles without altering the component's functionality or control flow.

Changes

File Change Summary
packages/theme/src/base-select/index.less Updated height properties for .base-select__tag and its variants to use new CSS variables. Reorganized CSS rules for &--small and &--mini classes.
packages/theme/src/base-select/vars.less Added new CSS custom properties for tag heights: --tv-BaseSelect-tag-height-default, --tv-BaseSelect-tag-height-medium, --tv-BaseSelect-tag-height-small, and --tv-BaseSelect-tag-height-mini.

Possibly related PRs

Suggested labels

enhancement

Suggested reviewers

  • zzcr

Poem

🐇 In the fields where tags do play,
With heights that flex and sway,
CSS variables now take the lead,
Making styles a joy indeed!
Hopping through the code with glee,
BaseSelect shines so beautifully! 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c974af3 and 61715b7.

📒 Files selected for processing (2)
  • packages/theme/src/base-select/index.less (1 hunks)
  • packages/theme/src/base-select/vars.less (1 hunks)
🔇 Additional comments (7)
packages/theme/src/base-select/vars.less (2)

64-71: LGTM! Well-structured CSS custom properties.

The new tag height variables follow a consistent naming pattern and calculation approach, subtracting 8px from their respective base heights. The implementation is clean and maintainable.


65-65: Verify the availability of referenced size variables.

The calculations reference base size variables (--tv-size-height-lg, -md, -sm, -xs). Let's ensure these variables are properly defined and available.

Also applies to: 67-67, 69-69, 71-71

✅ Verification successful

Based on the search results, I can see that the base size height variables are properly defined in the theme files:

  1. In packages/theme/src/base/vars.less:
--tv-size-height-xs: 24px; // mini 尺寸
--tv-size-height-sm: 28px; // small 尺寸
--tv-size-height-md: 32px; // medium 尺寸 - 默认
--tv-size-height-lg: 40px; // large 尺寸
  1. These variables are used consistently throughout the codebase, including in the BaseSelect component's tag height calculations:
--tv-BaseSelect-tag-height-medium: calc(var(--tv-size-height-lg) - 8px);

The referenced size variables are properly defined and available in the theme system.

The variables are defined in the base theme file and are widely used across multiple components, confirming their availability and proper integration into the theming system.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for the definition of base size height variables
# Expected: Find definitions of the base size variables in theme files

# Search for size height variable definitions
rg --type=less "tv-size-height-(lg|md|sm|xs)\s*[,:]" packages/theme/

# Search for potential imports that might define these variables
rg --type=less "@import.*size|height" packages/theme/

Length of output: 111463

packages/theme/src/base-select/index.less (5)

208-208: LGTM! Good use of CSS variable for default tag height.

The change from a fixed pixel value to a CSS variable improves maintainability and flexibility.


214-214: LGTM! Consistent implementation for medium size.

The change maintains consistency with the default size implementation.


218-222: LGTM! Well-structured small size implementation.

The changes maintain consistent spacing and follow a logical size progression in the codebase.


224-227: Verify CSS variable definitions in vars.less.

The implementation looks good, but we should verify that all the new CSS variables are properly defined in vars.less:

  • --tv-BaseSelect-tag-height-default
  • --tv-BaseSelect-tag-height-medium
  • --tv-BaseSelect-tag-height-small
  • --tv-BaseSelect-tag-height-mini
✅ Verification successful

All required CSS variables are properly defined in vars.less

The verification confirms that all necessary CSS variables for tag heights are correctly defined in vars.less:

  • --tv-BaseSelect-tag-height-default (based on md height)
  • --tv-BaseSelect-tag-height-medium (based on lg height)
  • --tv-BaseSelect-tag-height-small (based on sm height)
  • --tv-BaseSelect-tag-height-mini (based on xs height)

Each variable follows a consistent pattern of subtracting 8px from the corresponding base size height.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify CSS variable definitions in vars.less

# Check for the presence of all required CSS variables
rg --type less "tv-BaseSelect-tag-height-(default|medium|small|mini)" packages/theme/src/base-select/vars.less

Length of output: 410


208-227: Verify vertical alignment in collapsed state.

While the height changes look good, please verify that these modifications don't affect the vertical alignment of tags, particularly when:

  1. Multiple tags are present
  2. Tags are in a collapsed state
  3. The select component is disabled

This will ensure the changes don't introduce any visual regressions.

✅ Verification successful

Height changes are safe for vertical alignment

The changes to tag heights are well-supported by the existing layout system:

  • Tags container uses flexbox with align-items: center ensuring vertical centering
  • Proper padding and margins are defined through CSS variables
  • Tag spacing is consistently maintained through --tv-BaseSelect-tag-margin
  • Collapsed state is handled with specific styles and transformations

The vertical alignment will be maintained across all states because:

  1. Multiple tags: Flex layout handles multi-tag alignment
  2. Collapsed state: Uses transform: translateY(-50%) for centering
  3. Disabled state: Inherits the same layout properties
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Look for related vertical alignment styles

# Check for vertical alignment related properties
rg --type less "(vertical-align|align-items|display: flex)" packages/theme/src/base-select/

Length of output: 821


Script:

#!/bin/bash
# Let's check the context around these alignment properties and tag-related styles
rg --type less -B 2 -A 2 "(vertical-align|align-items|display: flex)" packages/theme/src/base-select/

# Also check for any tag-specific styles that might affect alignment
rg --type less -B 2 -A 2 "@{tag-prefix-cls}" packages/theme/src/base-select/

Length of output: 3685


Script:

#!/bin/bash
# Let's check tag-related styles with proper escaping
rg --type less -B 2 -A 2 "\@\{tag-prefix-cls\}" packages/theme/src/base-select/

# Also check for any styles related to tag positioning and spacing
rg --type less -B 2 -A 2 "(margin|padding|gap)" packages/theme/src/base-select/

Length of output: 6900


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.

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

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