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

fixed the logo in sponsors #3565

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

dewang002
Copy link

@dewang002 dewang002 commented Jan 11, 2025

Description

  • over here I just fix the size of logo in sponsore section.

  • before it look like this
    befor look

  • after it look like this
    contrubuiton

Related issue(s)
Fixes #3158

Summary by CodeRabbit

  • Style
    • Updated sponsor image styling across multiple sponsor lists
    • Modified imageClass properties to adjust height classes for responsive design
    • Refined image display and sizing for Gold, Silver, and main Sponsors lists

Copy link

coderabbitai bot commented Jan 11, 2025

Walkthrough

The pull request focuses on modifying the imageClass properties for sponsor lists across three different TypeScript files: GoldSponsorsList.ts, SilverSponsorsList.ts, and SponsorsList.ts. The changes primarily involve adjusting the height classes for sponsor logos, with a consistent pattern of adding explicit height classes (h-*) before the responsive screen-specific height classes (sm:h-*).

Changes

File Change Summary
components/sponsors/GoldSponsorsList.ts Updated imageClass from 'inline-block px-4 sm:h-14' to 'inline-block px-4 h-14 sm:h-14'
components/sponsors/SilverSponsorsList.ts Modified imageClass for multiple sponsors from 'inline-block sm:h-9' to 'inline-block h-9 sm:h-9'
components/sponsors/SponsorsList.ts Removed sm: prefix from height classes, changing from sm:h-12, sm:h-14, sm:h-18 to h-12, h-14, h-18

Assessment against linked issues

Objective Addressed Explanation
Normalize sponsor logo sizes [#3158]

Poem

🐰 Logos dancing, classes align
Height and width in perfect design
Sponsors' images, now just right
Responsive magic, pixel-perfect might!
CodeRabbit's touch, a styling delight 🎨

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

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.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Jan 11, 2025

We require all PRs to follow Conventional Commits specification.
More details 👇🏼

 No release type found in pull request title "fixed the logo in sponsors". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link

netlify bot commented Jan 11, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 5726cd0
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6782691a784d0f0008120a9a
😎 Deploy Preview https://deploy-preview-3565--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Jan 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (67b292a) to head (5726cd0).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3565   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           19        19           
  Lines          668       668           
=========================================
  Hits           668       668           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

🧹 Nitpick comments (1)
components/sponsors/SponsorsList.ts (1)

9-23: Consider extracting common sponsor image styles.

The current implementation duplicates height classes across multiple sponsors. Consider creating reusable Tailwind classes or using @apply to define sponsor image sizes. This would improve maintainability and ensure consistency across all sponsor components.

Example approach:

/* styles/sponsors.css */
.sponsor-image-sm {
  @apply inline-block px-4 h-12 sm:h-12;
}
.sponsor-image-md {
  @apply inline-block px-4 h-14 sm:h-14;
}
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 67b292a and 5726cd0.

📒 Files selected for processing (3)
  • components/sponsors/GoldSponsorsList.ts (1 hunks)
  • components/sponsors/SilverSponsorsList.ts (2 hunks)
  • components/sponsors/SponsorsList.ts (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • components/sponsors/GoldSponsorsList.ts
  • components/sponsors/SilverSponsorsList.ts
⏰ Context from checks skipped due to timeout of 180000ms (4)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Lighthouse CI
🔇 Additional comments (2)
components/sponsors/SponsorsList.ts (2)

9-9: LGTM! Consistent height across breakpoints.

The addition of the default height class ensures consistent logo sizing, preventing layout shifts during page load.


16-16: LGTM! Maintains consistent pattern.

The change follows the established pattern of setting default heights matching the responsive breakpoint heights.

},
{
name: 'Postman',
website: 'https://www.postman.com',
imageSrc: '/img/sponsors/postman.png',
altText: 'Postman',
imageClass: 'inline-block px-4 sm:h-18'
imageClass: 'inline-block px-4 h-18 sm:h-18'
Copy link

Choose a reason for hiding this comment

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

💡 Codebase verification

Use h-72 instead of h-18 for 18rem height

The h-18 class is not defined in your Tailwind configuration. To achieve a height of 18rem, use h-72 which is properly configured in your tailwind.config.ts:

height: {
  72: '18rem',
  // ...
}
🔗 Analysis chain

Verify the custom height class.

The h-18 class is not a standard Tailwind CSS class. Please verify if this is defined in your Tailwind configuration.

Let's check the Tailwind configuration:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for custom height configuration in Tailwind config files
fd -e js -e ts -e json "tailwind" | xargs rg -l "height|spacing.*18"

Length of output: 87


Script:

#!/bin/bash
# View the contents of tailwind.config.ts
cat tailwind.config.ts

Length of output: 5771

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.

2 participants