Skip to content

fix: mobile navbar overflow + README port/setup corrections#45

Open
Priyanshu-byte-coder wants to merge 1 commit into
kunalverma2512:mainfrom
Priyanshu-byte-coder:fix/mobile-navbar-overflow
Open

fix: mobile navbar overflow + README port/setup corrections#45
Priyanshu-byte-coder wants to merge 1 commit into
kunalverma2512:mainfrom
Priyanshu-byte-coder:fix/mobile-navbar-overflow

Conversation

@Priyanshu-byte-coder
Copy link
Copy Markdown

@Priyanshu-byte-coder Priyanshu-byte-coder commented May 14, 2026

Summary

Changes

  • frontend/src/components/shared/Navbar.jsx — mobile menu div gets scrollable max-height
  • README.md — port fix + MongoDB Atlas setup + SMTP setup + Troubleshooting section
  • frontend/.env.example — new file with VITE_API_BASE_URL=http://localhost:8000/api

Test plan

  • On mobile/small viewport, expand Tools in navbar — Login/Signup should stay reachable by scrolling
  • Desktop layout unchanged
  • Follow README MongoDB Atlas steps — connection string format is correct
  • Follow README SMTP steps — Gmail App Password instructions are accurate

Summary by CodeRabbit

  • Documentation

    • Updated development setup guide with correct port configuration
    • Added MongoDB Atlas setup instructions
    • Added SMTP configuration guide (Gmail and Mailtrap)
    • Added troubleshooting reference for common configuration issues
  • Bug Fixes

    • Fixed mobile menu overflow by adding scroll support

Review Change Stack

… docs

- Add max-h and overflow-y-auto to mobile menu so auth buttons stay accessible when Tools section expands
- Fix port references in README (5000 -> 8000) to match server/.env.example
- Create frontend/.env.example with correct VITE_API_BASE_URL
- Add MongoDB Atlas, SMTP setup guides and troubleshooting table to README
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 14, 2026

📝 Walkthrough

Walkthrough

This PR addresses setup onboarding issues and mobile navigation usability by synchronizing documented port configurations across frontend and backend to 8000, adding MongoDB Atlas and SMTP setup guides with troubleshooting reference, and improving mobile menu scrolling behavior in the Navbar component.

Changes

Development Setup and Configuration Synchronization

Layer / File(s) Summary
Port configuration synchronization
README.md, frontend/.env.example
Backend port example updated from 5000 to 8000 in README environment variables and setup instructions. New frontend/.env.example documents VITE_API_BASE_URL pointing to http://localhost:8000/api with guidance to match backend PORT configuration.
MongoDB Atlas and SMTP configuration guides
README.md
New "MongoDB Atlas Setup" section provides step-by-step instructions and example MONGO_URI. New "SMTP Setup" section documents Gmail App Password configuration and Mailtrap as alternative, with example server/.env variables.
Troubleshooting reference table
README.md
New "Troubleshooting" section provides table of common misconfiguration issues (port mismatch, MongoDB URI/IP connectivity, SMTP credentials, missing JWT secret) with resolutions.

Mobile Navigation Usability

Layer / File(s) Summary
Mobile menu height and scroll constraints
frontend/src/components/shared/Navbar.jsx
Mobile menu wrapper <div> now uses max-h-[calc(100vh-4rem)] and overflow-y-auto to constrain height and enable vertical scrolling, preventing content from overflowing off-screen on smaller devices.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Poem

A rabbit hops through docs with cheer,
Port 8000 now crystal clear! 📱
Mobile menus scroll with grace,
No overflow in this place.
Setup guides make onboarding bright,
MongoDB, SMTP—all done right! 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main changes: fixing mobile navbar overflow and updating README with port/setup corrections, matching the actual changeset content.
Linked Issues check ✅ Passed All code changes directly address the objectives in linked issues #38 and #41: mobile menu scrolling, port synchronization, .env documentation, and MongoDB/SMTP setup guides are fully implemented.
Out of Scope Changes check ✅ Passed All changes are directly scoped to the linked issues; README updates address issue #41 requirements and Navbar changes address issue #38 mobile usability requirements.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

🚀 PR Received Successfully

Hello @Priyanshu-byte-coder,

Thank you for taking the initiative to contribute to this project.

Please ensure that your PR follows all project guidelines properly before requesting review.

⚠️ Important Instructions

  • Maintain proper code quality and structure
  • Do not make unnecessary changes/files
  • Ensure responsiveness across devices
  • Follow existing project conventions strictly
  • Attach screenshots/videos for UI-related changes
  • Resolve merge conflicts before requesting review
  • Avoid AI-generated low quality PRs or copied implementations

📌 Mandatory for GSSoC'26 Participants

Joining the community group and announcement channel is compulsory for all contributors participating through GSSoC'26.

Failure to follow contribution guidelines may lead to PR rejection.

We appreciate your effort and wish you a great open-source journey ahead. ✨

Copy link
Copy Markdown

@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)
README.md (1)

867-916: ⚡ Quick win

Make the new setup sections discoverable from the Table of Contents.

MongoDB Atlas Setup, SMTP Setup, and Troubleshooting were added but are not linked in the ToC, which hurts onboarding navigation. Consider adding ToC anchors (and optionally placing these sections before License).

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 867 - 916, The README added three new sections
("MongoDB Atlas Setup", "SMTP Setup", "Troubleshooting") but they are not
referenced from the Table of Contents; update the ToC to include anchor links to
these headers and ensure the headers use consistent markdown heading levels
(e.g., "### MongoDB Atlas Setup", "### SMTP Setup", "### Troubleshooting") so
anchors work, or move these sections before the "License" section if preferred;
add entries in the TOC like "MongoDB Atlas Setup", "SMTP Setup", and
"Troubleshooting" pointing to their markdown anchors so readers can navigate to
those sections easily.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 874: Replace the README guidance that suggests adding "0.0.0.0/0" under
Network Access with a least-privilege recommendation: instruct users to add only
necessary IP ranges or specific CIDRs for their environment and to avoid using
0.0.0.0/0 except as a temporary, short-lived fallback; if you keep mention of
0.0.0.0/0 include an explicit, prominent warning about the security risk and
require steps to remove it before production.

---

Nitpick comments:
In `@README.md`:
- Around line 867-916: The README added three new sections ("MongoDB Atlas
Setup", "SMTP Setup", "Troubleshooting") but they are not referenced from the
Table of Contents; update the ToC to include anchor links to these headers and
ensure the headers use consistent markdown heading levels (e.g., "### MongoDB
Atlas Setup", "### SMTP Setup", "### Troubleshooting") so anchors work, or move
these sections before the "License" section if preferred; add entries in the TOC
like "MongoDB Atlas Setup", "SMTP Setup", and "Troubleshooting" pointing to
their markdown anchors so readers can navigate to those sections easily.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 85af6b01-009d-4155-9f7d-e7fe9d6c9c70

📥 Commits

Reviewing files that changed from the base of the PR and between 12e4428 and ea59034.

📒 Files selected for processing (3)
  • README.md
  • frontend/.env.example
  • frontend/src/components/shared/Navbar.jsx

Comment thread README.md
1. Go to [cloud.mongodb.com](https://cloud.mongodb.com) and create a free account
2. Create a new **Cluster** (free M0 tier works fine)
3. Under **Database Access**, create a user with read/write permissions
4. Under **Network Access**, add your IP (or `0.0.0.0/0` for development)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Avoid recommending 0.0.0.0/0 as a default Atlas network rule.

This guidance weakens security posture and is easy to copy into non-dev environments. Prefer recommending least-privilege IP allowlists, with 0.0.0.0/0 only as a short-lived fallback plus explicit warning.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 874, Replace the README guidance that suggests adding
"0.0.0.0/0" under Network Access with a least-privilege recommendation: instruct
users to add only necessary IP ranges or specific CIDRs for their environment
and to avoid using 0.0.0.0/0 except as a temporary, short-lived fallback; if you
keep mention of 0.0.0.0/0 include an explicit, prominent warning about the
security risk and require steps to remove it before production.

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

Labels

None yet

Projects

None yet

1 participant