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

docs(button): [button] update image button demo #2464

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

kagol
Copy link
Member

@kagol kagol commented Oct 29, 2024

PR

效果如下:
image

之前的效果:
image

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

Summary by CodeRabbit

  • New Features

    • Updated button images across components to improve visual representation.
    • Enhanced button layout with flexible alignment for better display of icons and text.
  • Bug Fixes

    • Removed width attribute from img tags to improve image rendering.
  • Style

    • Introduced scoped styles to prevent style leakage between components.
    • Adjusted button display properties for improved alignment and layout.

Copy link

coderabbitai bot commented Oct 29, 2024

Walkthrough

The changes in this pull request involve updates to two Vue component files (image-composition-api.vue and image.vue) and a LESS file (index.less). Both Vue components have had their image sources changed from email.png to button-image.png, and the width attribute in the img tags has been removed. Additionally, both components now include the scoped attribute in their style sections. The LESS file has modifications to the button's display properties, changing it from inline-block to inline-flex and adding vertical centering for better alignment of button contents.

Changes

File Change Summary
examples/sites/demos/pc/app/button/image-composition-api.vue, examples/sites/demos/pc/app/button/image.vue Updated image source from email.png to button-image.png, removed width attribute from img tags, and added scoped attribute to <style>.
packages/theme/src/button/index.less Changed button class display from inline-block to inline-flex and added align-items: center for vertical alignment.

Possibly related PRs

Suggested reviewers

  • zzcr

Poem

🐇 In the meadow where buttons gleam,
A new image shines, like a sweet dream.
With styles scoped and centered tight,
Our buttons now dance in pure delight!
Hopping along, we celebrate the change,
In our vibrant world, nothing feels strange! 🌼


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

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

🧹 Outside diff range and nitpick comments (3)
examples/sites/demos/pc/app/button/image.vue (3)

3-3: LGTM! Consider adding comments for better documentation.

Since this is a demo file, consider adding comments to explain the purpose of removing the inline width attribute in favor of CSS styling.

 <tiny-button class="demo-button">
+  <!-- Image size is controlled via CSS for better maintainability -->
   <img :src="image" />

17-17: Add comments explaining the environment configuration.

Since this is a demo file, it would be helpful to document the required environment setup.

 data() {
   return {
+    // VITE_APP_BUILD_BASE_URL is required in the environment for proper asset loading
     image: `${import.meta.env.VITE_APP_BUILD_BASE_URL}static/images/button-image.png`
   }
 }

Line range hint 23-33: Document styling decisions for better demo clarity.

The styles are well-structured, but since this is a demo file, consider adding comments to explain the styling choices.

 <style scoped>
+/* Button image styles - maintains consistent sizing and spacing */
 .demo-button img {
   width: 16px;
   height: 16px;
   margin-right: 8px;
   border-radius: 2px;
 }
+/* Button text styles - ensures vertical alignment with the image */
 .demo-button span {
   height: 16px;
   line-height: 16px;
 }
 </style>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f6f512f and 5733029.

⛔ Files ignored due to path filters (2)
  • examples/sites/public/static/images/button-image.png is excluded by !**/*.png
  • examples/sites/public/static/images/email.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • examples/sites/demos/pc/app/button/image-composition-api.vue (1 hunks)
  • examples/sites/demos/pc/app/button/image.vue (2 hunks)
  • packages/theme/src/button/index.less (1 hunks)
🔇 Additional comments (2)
examples/sites/demos/pc/app/button/image-composition-api.vue (1)

Line range hint 14-24: LGTM! Well-structured styles.

The addition of scoped styles and the consistent sizing of button elements are good practices. The styles are well-organized and provide a clean layout for the button component.

packages/theme/src/button/index.less (1)

11-12: Improved button content alignment with flexbox.

The change from inline-block to inline-flex along with align-items: center is a good improvement that:

  • Provides better vertical alignment control for button content
  • Ensures consistent centering of images, icons, and text
  • Aligns with modern flexbox best practices

Please verify the button's appearance with various content combinations:

  • Text only
  • Icon + text
  • Image + text
  • Long text that wraps
  • RTL text direction

<span>图片按钮</span>
</tiny-button>
</template>

<script setup>
import { TinyButton } from '@opentiny/vue'

const image = `${import.meta.env.VITE_APP_BUILD_BASE_URL}static/images/email.png`
const image = `${import.meta.env.VITE_APP_BUILD_BASE_URL}static/images/button-image.png`
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider centralizing asset paths.

While using environment variables is good, consider moving the static asset paths to a centralized configuration file for better maintainability.

Create a config file for asset paths:

// constants/assets.js
export const IMAGES = {
  BUTTON: {
    ICON: `${import.meta.env.VITE_APP_BUILD_BASE_URL}static/images/button-image.png`
  }
}

Then import and use it:

-const image = `${import.meta.env.VITE_APP_BUILD_BASE_URL}static/images/button-image.png`
+import { IMAGES } from '@/constants/assets'
+const image = IMAGES.BUTTON.ICON

@@ -1,17 +1,17 @@
<template>
<tiny-button class="demo-button">
<img :src="image" width="26" />
<img :src="image" />
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add alt text for accessibility.

The image lacks an alt attribute which is important for screen readers and accessibility compliance.

-    <img :src="image" />
+    <img :src="image" alt="Button icon" />
📝 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
<img :src="image" />
<img :src="image" alt="Button icon" />

@kagol kagol merged commit 2e6e2f8 into dev Nov 4, 2024
8 of 10 checks passed
@kagol kagol deleted the kagol/update-image-button-demo branch November 4, 2024 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant