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 footer not sticky on the bottom #1173

Closed

Conversation

lindotex
Copy link

@lindotex lindotex commented Oct 24, 2024

# ✨ Codu Pull Request 💻

Fixes #1171

Pull Request details

  • Added an min height to the post component. (tiny small change), because I didn't want to make any huge alterations on the code.

Any Breaking changes

  • None

Associated Screenshots

Desktop:
desktop view of the page

Mobile:
mobile view of the page

added an new className "min-h-96" to the div where the post tabs are located.
I added an extra className "min-h-96" on the div
containing the post tabs.That made the footer goes
to the bottom of the page. I tried to make the
Footer get Sticked to the bottom, using an
"sticky bottom-0" on the Footer, but it didn't
work. The component must be flex.
@lindotex lindotex requested a review from a team as a code owner October 24, 2024 16:53
Copy link

vercel bot commented Oct 24, 2024

@lindotex is attempting to deploy a commit to the Codú Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Oct 24, 2024

Walkthrough

The changes introduced in this pull request involve modifications to the layout of the MyPosts component and the RootLayout component. The MyPosts component's class was updated to enhance its width responsiveness, while the RootLayout component was wrapped in a grid container to improve the overall layout structure. No functionality related to post handling, error management, or user session fetching was altered.

Changes

File Change Summary
app/(app)/my-posts/_client.tsx Updated class of div element to include w-auto and sm:w-full for improved layout flexibility.
app/(app)/layout.tsx Added a <div> with a grid layout wrapping Nav, children, and Footer components.

Assessment against linked issues

Objective Addressed Explanation
Footer should stick to the bottom on the new post page (#1171)

Possibly related PRs

Suggested labels

hacktoberfest-accepted, hacktoberfest

Suggested reviewers

  • NiallJoeMaher

Poem

In the land of posts, where rabbits play,
A footer now sticks, come what may.
With grids and widths, we dance and cheer,
Layouts so fine, the changes are here! 🐇✨
Hop along, dear friends, let's celebrate,
A better view, oh, isn't it great?


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

Hello @lindotex, thanks for opening your first Pull Request. The maintainers will review this Pull Request and provide feedback as soon as possible. Keep up the great work!

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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 051f633 and ce501d5.

📒 Files selected for processing (2)
  • app/(app)/my-posts/_client.tsx (1 hunks)
  • sample.env (0 hunks)
💤 Files with no reviewable changes (1)
  • sample.env
🔇 Additional comments (1)
app/(app)/my-posts/_client.tsx (1)

111-111: Implementation looks good, but verify the target page.

The addition of min-h-96 class is a valid approach to ensure the container maintains minimum height, which helps with sticky footer positioning.

However, there seems to be a discrepancy. The PR description mentions fixing the footer issue on the "New Post" page, but this change is in the "My Posts" page component. Let's verify the correct target:

@@ -108,7 +108,7 @@ const MyPosts = () => {
cancelText="Cancel"
/>
)}
<div className="relative mx-4 max-w-2xl bg-neutral-100 dark:bg-black sm:mx-auto">
<div className="relative mx-4 min-h-96 max-w-2xl bg-neutral-100 dark:bg-black sm:mx-auto">
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider a more robust layout solution.

While adding minimum height works, consider implementing a more robust sticky footer solution using flex layout to ensure consistent behavior across all pages:

-      <div className="relative mx-4 min-h-96 max-w-2xl bg-neutral-100 dark:bg-black sm:mx-auto">
+      <div className="relative mx-4 flex min-h-[calc(100vh-theme('spacing.header'))] max-w-2xl flex-col bg-neutral-100 dark:bg-black sm:mx-auto">

This approach:

  • Uses viewport height calculation
  • Accounts for header height (adjust theme('spacing.header') to match your header height)
  • Ensures content fills available space
  • Works consistently across all viewport sizes

Committable suggestion was skipped due to low confidence.

Copy link

vercel bot commented Oct 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
codu ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 26, 2024 10:37pm

Copy link
Contributor

@NiallJoeMaher NiallJoeMaher left a comment

Choose a reason for hiding this comment

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

The env should not be deleted and the min-h-96 might be too high or low depending on the screen size.

added an grid behavior on the layout, specifying that the children component must fill the available space. That way, the footer will be always placed at the bottom.
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 (1)
app/(app)/layout.tsx (1)

82-90: Consider adding semantic main wrapper.

While the current implementation works well, consider wrapping the children with a semantic main tag for better accessibility and HTML structure.

 <div className="grid min-h-screen grid-rows-[auto_1fr_auto]">
   <Nav
     session={session}
     algoliaSearchConfig={algoliaSearchConfig}
     username={userData?.username || null}
   />
-  {children}
+  <main>{children}</main>
   <Footer />
 </div>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ce501d5 and 6feef43.

📒 Files selected for processing (2)
  • app/(app)/layout.tsx (1 hunks)
  • app/(app)/my-posts/_client.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/(app)/my-posts/_client.tsx
🔇 Additional comments (1)
app/(app)/layout.tsx (1)

82-90: LGTM! Robust solution for sticky footer.

The implementation using CSS Grid with grid-rows-[auto_1fr_auto] is an excellent choice for ensuring the footer stays at the bottom. This approach:

  • Automatically adjusts to content height
  • Works consistently across browsers
  • Maintains layout with minimal content

@NiallJoeMaher
Copy link
Contributor

Just need npm run prettier:fix

@@ -79,13 +79,15 @@ export default async function RootLayout({

return (
<>
Copy link
Contributor

Choose a reason for hiding this comment

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

No longer need the fragments. Let me know if you have time to update this.

@NiallJoeMaher
Copy link
Contributor

You can reopen if you decide to tackle again.

@lindotex
Copy link
Author

Sorry by my late answer.
I was Traveling 😅...
I have the code ready.

@Zaid-B24
Copy link
Contributor

Zaid-B24 commented Nov 3, 2024

I can work on this issue, if no one has any problem with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Footer does't stick to the bottom when we are on the new post page
3 participants