83c2102afe
SettingsShell always passed the literal string "/settings" as currentPage to TabNavigation, regardless of the actual sub-route. TabNavigation's isExactRoot check (currentPage === tab.href) was therefore always true for the settings tab, so tapping it while on any settings sub-page (e.g. /settings/wallet) always hit the "already here" branch and called preventDefault() instead of navigating — the user had to tap a different tab first (which uses a different pathname) before tapping Settings again would actually work. Now passes the real pathname; tab highlighting is unaffected since TabNavigation already does its own startsWith() check for that. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.