-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
footer layout for mobile #461
Conversation
@jainaryan04 is attempting to deploy a commit to the bunty's projects Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughThe changes in this pull request involve updates to the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
There was a problem hiding this 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 (1)
README.md (1)
283-284
: Replace hard tabs with spaces for consistent formatting.Several lines in the table structure use hard tabs instead of spaces. While this doesn't affect the rendered output, it's best to maintain consistent indentation using spaces throughout the markdown file.
- </tr> - <tr> + </tr> + <tr>Also applies to: 327-328, 371-372, 591-592, 635-636
🧰 Tools
🪛 Markdownlint
283-283: Column: 1
Hard tabs(MD010, no-hard-tabs)
284-284: Column: 1
Hard tabs(MD010, no-hard-tabs)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
README.md
(7 hunks)frontend/src/components/Shared/footer/Content.jsx
(3 hunks)
🧰 Additional context used
🪛 Markdownlint
README.md
283-283: Column: 1
Hard tabs
(MD010, no-hard-tabs)
284-284: Column: 1
Hard tabs
(MD010, no-hard-tabs)
327-327: Column: 1
Hard tabs
(MD010, no-hard-tabs)
328-328: Column: 1
Hard tabs
(MD010, no-hard-tabs)
371-371: Column: 1
Hard tabs
(MD010, no-hard-tabs)
372-372: Column: 1
Hard tabs
(MD010, no-hard-tabs)
591-591: Column: 1
Hard tabs
(MD010, no-hard-tabs)
592-592: Column: 1
Hard tabs
(MD010, no-hard-tabs)
635-635: Column: 1
Hard tabs
(MD010, no-hard-tabs)
636-636: Column: 1
Hard tabs
(MD010, no-hard-tabs)
🔇 Additional comments (5)
frontend/src/components/Shared/footer/Content.jsx (3)
9-9
: LGTM! Responsive layout improvements
The changes to the main container's layout classes improve the mobile experience by:
- Properly centering content on mobile with
items-center
- Maintaining left alignment on desktop with
md:items-start
- Using appropriate padding with
md:px-12
202-202
: LGTM! Improved contact section alignment
The contact section's alignment has been improved with:
- Centered alignment on mobile with
items-center
- Left alignment on desktop with
md:items-start
- Better spacing with
pb-8
170-170
: Verify the margin adjustments
The margin changes look good and address the uneven margin issue mentioned in #434. Let's verify the implementation across different screen sizes.
✅ Verification successful
Margin adjustments are correctly implemented
The margin changes in the footer component are consistent and well-structured:
- The main container uses responsive margins (
mx-[40px] md:ml-[30px] md:mr-0
) for proper alignment - The newsletter section uses
mx-auto
for centered positioning - The Google Translate image margin (
mr-[65px]
) is currently commented out
The implementation properly addresses the uneven margin issue (#434) while maintaining a consistent responsive layout.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for any other margin-related classes that might need similar adjustments
# Search for margin classes that might need responsive variants
rg -g '*.jsx' -g '*.js' 'className="[^"]*m[lrxy]-\['
Length of output: 310
Script:
#!/bin/bash
# Let's check the entire footer component for margin-related classes to ensure consistency
rg -g '*.jsx' -g '*.js' -A 2 -B 2 'className="[^"]*\b(m[lrxy]|margin)[^"]*"' frontend/src/components/Shared/footer/
Length of output: 1489
README.md (2)
276-282
: LGTM! New contributor entries are well-structured.
The additions and modifications to the contributors section maintain consistent formatting with existing entries. Each entry properly includes:
- GitHub avatar
- Profile link
- Contributor name
Also applies to: 293-297, 307-311, 314-318, 425-429, 432-436, 577-583, 584-590, 637-642
Line range hint 276-642
: Verify contributor profile links.
The changes look good, but it's important to ensure all GitHub profile links are correct and active.
✅ Verification successful
All GitHub profile links are valid and active
All the checked GitHub profiles are accessible and active. Each profile link correctly maps to an existing GitHub user account with recent activity, confirming the validity of the contributors' section.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify that all new/modified GitHub profile links are valid
# Test: Check HTTP status codes for new/modified profile URLs
echo "Verifying GitHub profile links..."
gh api \
-H "Accept: application/vnd.github+json" \
-H "X-GitHub-Api-Version: 2022-11-28" \
/users/Ashwinib26 /users/itznayan /users/Shirisha-16 /users/Sourabh782 \
/users/AE-Hertz /users/Navneetdadhich /users/souvikpramanikgit /users/myselfshivams \
/users/Hemraj-7
Length of output: 364
Script:
#!/bin/bash
# Check GitHub profiles one by one
echo "Checking GitHub profiles..."
for user in Ashwinib26 itznayan Shirisha-16 Sourabh782 AE-Hertz Navneetdadhich souvikpramanikgit myselfshivams Hemraj-7; do
echo "Checking $user..."
gh api -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" "/users/$user"
done
Length of output: 14112
🧰 Tools
🪛 Markdownlint
283-283: Column: 1
Hard tabs
(MD010, no-hard-tabs)
284-284: Column: 1
Hard tabs
(MD010, no-hard-tabs)
@jainaryan04 resolve the conflicts |
done @RamakrushnaBiswal |
@RamakrushnaBiswal pls merge |
13955cc
into
RamakrushnaBiswal:main
closes #434
@RamakrushnaBiswal
fix footer layout for mobile
Summary by CodeRabbit
Documentation
Style