Skip to content

PR_DESCRIPTION.md

Latest commit

 

History

History
25 lines (21 loc) · 2.13 KB

PR_DESCRIPTION.md

File metadata and controls

25 lines (21 loc) · 2.13 KB
Raw

Fix: Add "Request Invite" Button to Mobile Nav (Pre-Login)

Description

This PR addresses Issue #251 by adding a visible "Request Invite" button to the mobile navigation header for unauthenticated users. It also introduces a cleaner /invite route and ensures consistent behavior across the application.

Changes

  • Added /invite Route: Created a new route in mui-routes.jsx that maps to the RequestAccessPage.
  • Routing Fix: Updated main.jsx and Auth.jsx to correctly handle the top-level /invite route using the AuthLayout.
  • Navbar Fix: Updated AuthNavbar.jsx to ensure navigation buttons (Go Back, Login) appear correctly on the /invite route, and updated the "Get Access" link on the login page to point to /invite.
  • Mobile Header Update: Added a "Request Invite" button to the MainNavBar toolbar.
    • Positioning: Grouped the button with the hamburger menu using a flex container to ensure they appear together on the right side of the toolbar.
    • Visibility: Visible only on mobile screens (Hidden mdUp) when the user is not logged in.
  • Route Updates: Updated existing "Request Invite" buttons (desktop and mobile drawer) to use the new /invite route.
  • Auth Redirect: Updated requireAuth in auth.js to redirect to /invite instead of /auth/request-access.
  • UX Improvements: The "Request Invite" button is hidden if the user is already on the /invite page to prevent redundant navigation.

Verification

  • Mobile View: Confirmed that the "Request Invite" button appears in the header on mobile screens for unauthenticated users, positioned correctly next to the menu icon.
  • Navigation: Verified that clicking the button navigates to /invite.
  • Layout: Verified that /invite renders with the correct AuthLayout and that the AuthNavbar buttons (Go Back, Login) are visible.
  • Visibility Logic: Confirmed the button is hidden when logged in or when already on the /invite page.
  • Backward Compatibility: The old /auth/request-access route remains functional (via the component mapping), but the app now prefers /invite.

Related Issue

Fixes #251