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: improve ant design button icon style #4520

Merged
merged 1 commit into from
Sep 26, 2024
Merged

fix: improve ant design button icon style #4520

merged 1 commit into from
Sep 26, 2024

Conversation

anncwb
Copy link
Collaborator

@anncwb anncwb commented Sep 26, 2024

Description

fixed #4517

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
  • Run the tests with pnpm test.
  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • New Features

    • Introduced enhanced styles for form validation, improving visual feedback for error states in form components.
    • Updated button styles for better alignment and display of icons.
  • Style

    • Reorganized CSS for improved structure and maintainability.

@anncwb anncwb added the bug Something isn't working label Sep 26, 2024
@anncwb anncwb requested a review from vince292007 as a code owner September 26, 2024 14:32
Copy link

changeset-bot bot commented Sep 26, 2024

⚠️ No Changeset found

Latest commit: cf89662

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Sep 26, 2024

Walkthrough

The changes in this pull request primarily focus on enhancing the CSS styles for form validation and button components in the Ant Design framework. Key modifications include the addition of styles for the .ant-btn class and adjustments to the .form-valid-error class, which now encapsulates error state styles for various input components. These changes aim to improve the visual feedback for users interacting with form elements.

Changes

File Change Summary
packages/styles/src/antd/index.css Added new styles for .ant-btn and adjusted .form-valid-error to include error state styles for .ant-select, .ant-input-number, and .ant-input-affix-wrapper.

Assessment against linked issues

Objective Addressed Explanation
Ensure button icons are centered (Issue #4517) It is unclear if the button icon alignment issue is resolved by the CSS changes.

Possibly related PRs

Suggested reviewers

  • vince292007

Poem

In the garden of code, where styles bloom bright,
Buttons and forms dance in the light.
With colors of error now clear to see,
A joyful update, as fresh as can be!
Hop along, dear developers, let’s fix and delight,
For every small change brings a new spark of light! 🐇✨


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
Contributor

@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: 0

🧹 Outside diff range and nitpick comments (2)
packages/styles/src/antd/index.css (2)

21-30: Good enhancement of form validation error styles.

The new styles for .form-valid-error improve the visual feedback for form validation errors, particularly for select components. The use of CSS custom properties for colors is a good practice.

For consistency, consider using the same CSS custom property for the box-shadow color:

 .ant-select-focused .ant-select-selector {
-  box-shadow: 0 0 0 2px rgb(255 38 5 / 6%) !important;
+  box-shadow: 0 0 0 2px hsl(var(--destructive) / 6%) !important;
 }

This change would make it easier to maintain consistent colors across the application.


32-41: Good addition of error styles for number and password inputs.

The new styles for number input and password input components in error states provide consistent visual feedback across different form elements. This enhances the overall user experience when dealing with form validation errors.

For better consistency and maintainability, consider the following changes:

  1. Use CSS custom properties for colors consistently:
 .ant-input-number-focused {
-  box-shadow: 0 0 0 2px rgb(255 38 5 / 6%);
+  box-shadow: 0 0 0 2px hsl(var(--destructive) / 6%);
 }

 .ant-input-affix-wrapper:hover {
   border-color: hsl(var(--destructive));
-  box-shadow: 0 0 0 2px rgb(255 38 5 / 6%);
+  box-shadow: 0 0 0 2px hsl(var(--destructive) / 6%);
 }
  1. Consider adding a focused state for the password input (.ant-input-affix-wrapper) to match the behavior of other input types:
.ant-input-affix-wrapper-focused {
  border-color: hsl(var(--destructive));
  box-shadow: 0 0 0 2px hsl(var(--destructive) / 6%);
}

These changes will improve consistency across different input types and make future maintenance easier.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8250894 and cf89662.

📒 Files selected for processing (1)
  • packages/styles/src/antd/index.css (1 hunks)
🔇 Additional comments (2)
packages/styles/src/antd/index.css (2)

10-14: Excellent fix for button icon alignment!

This change directly addresses the issue mentioned in #4517 by setting the .anticon within buttons to display: inline-flex. This approach is effective for centering icons within buttons and aligns with the Ant Design specifications.


Line range hint 1-41: Overall, these changes significantly improve button icon alignment and form validation styles.

The modifications in this file successfully address the main objective of the PR by fixing the button icon alignment issue. Additionally, the enhancements to form validation error styles provide a more consistent and user-friendly experience across different input types.

Key improvements:

  1. Button icon alignment is fixed using display: inline-flex.
  2. Consistent error styles are applied to select, number input, and password input components.
  3. CSS custom properties are used for most color definitions, improving maintainability.

The suggested minor improvements in the previous comments will further enhance the consistency and maintainability of the styles. Great work on improving the overall user interface!

@anncwb anncwb merged commit 17fa8eb into main Sep 26, 2024
14 checks passed
@anncwb anncwb deleted the bugfix/4517 branch September 26, 2024 14:40
@github-actions github-actions bot locked and limited conversation to collaborators Oct 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: ant-design-vue应用中,button按钮搭配图标展示时,没有跟ant官方一样
1 participant