Support page feature

[Hugo0]

• added landing page button and footer link for /support

- unlocked /support for guests

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
peanut-wallet	Ready	Preview	Comment	Sep 9, 2025 11:48am

[coderabbitai]

Walkthrough

Adds /support as a recognized public path and updates auth gating to respect public paths; exposes Support entry points via a footer link, a “Talk to Support” CTA in the LandingPage security section, and a “Contact Support” button on the error page.

Changes

Cohort / File(s)	Summary
Routing & auth gating src/app/(mobile-ui)/layout.tsx	Extended publicPathRegex to include /support; added clarifying comment; compute isPublicPath and updated readiness/auth gating to skip auth/loading when on public paths.
Error page support action src/app/[...recipient]/error.tsx	Imported useRouter from next/navigation; added “Contact Support” button that router.push('/support'); adjusted Card.Content layout to flex flex-col gap-3.
Landing page UI (Footer & Security CTA) src/components/LandingPage/Footer.tsx, src/components/LandingPage/securityBuiltIn.tsx	Footer: added “Support” link to /support and removed “Privacy” link. SecurityBuiltIn: imported Button and added conditional “Talk to Support” CTA (for feature.id === 3) linking to /support.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Prod release fixes #844 — Also modifies publicPathRegex in src/app/(mobile-ui)/layout.tsx to change recognized public routes.
• added tg footer #1144 — Updates src/components/LandingPage/Footer.tsx navigation/footer links, overlapping footer changes.
• [TASK-12771] Feat/new landing page #974 — Touches src/components/LandingPage/securityBuiltIn.tsx, related to the added security CTA.

Suggested reviewers

• Zishan-7

Pre-merge checks (1 passed, 1 warning, 1 inconclusive)

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	Title “Support page feature” refers to the main change but is too generic, lacking specifics on what aspects of the support page are implemented and how it affects the application.	Consider renaming the title to something more descriptive, for example “Add support page route for guests and UI links on landing page and footer,” which clearly summarizes the key additions.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	The description succinctly outlines the key changes of adding a landing page button and footer link for “/support” and unlocking the page for guest users, which directly corresponds to the pull request’s updates.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 70c8bac and 4e38ebb.

📒 Files selected for processing (1)

• src/app/[...recipient]/error.tsx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/app/[...recipient]/error.tsx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy-Preview

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch support-page-feature

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[notion-workspace]

/support

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fa07163 and 70c8bac.

📒 Files selected for processing (4)

• src/app/(mobile-ui)/layout.tsx (2 hunks)
• src/app/[...recipient]/error.tsx (2 hunks)
• src/components/LandingPage/Footer.tsx (1 hunks)
• src/components/LandingPage/securityBuiltIn.tsx (2 hunks)

🧰 Additional context used

🧬 Code graph analysis (2)

src/app/[...recipient]/error.tsx (1)

src/components/0_Bruddle/Button.tsx (1)

• Button (76-267)

src/components/LandingPage/securityBuiltIn.tsx (1)

src/components/0_Bruddle/Button.tsx (1)

• Button (76-267)

🪛 GitHub Actions: Tests

src/app/[...recipient]/error.tsx

[warning] 1-1: Prettier formatting issue detected in src/app/[...recipient]/error.tsx. Run 'prettier --write' to fix.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy-Preview

🔇 Additional comments (8)

src/components/LandingPage/Footer.tsx (1)

60-62: LGTM! Support link added successfully.

The Support link is properly integrated into the footer navigation with consistent styling and appropriate linking to /support.

src/components/LandingPage/securityBuiltIn.tsx (2)

2-2: LGTM! Button import added correctly.

The Button component import is properly added to support the new CTA functionality.

---

85-96: LGTM! Well-implemented conditional CTA.

The "Talk to Support" button is properly conditional to feature ID 3, uses appropriate styling, and correctly links to /support. The implementation is clean and follows the existing component patterns.

src/app/[...recipient]/error.tsx (3)

5-5: LGTM! Router import added for navigation.

The useRouter import is correctly added to enable client-side navigation to the support page.

---

8-8: LGTM! Router instance created properly.

The router instance is correctly initialized for navigation functionality.

---

22-22: LGTM! Improved layout with flex column.

The Card.Content layout is enhanced with flex column and gap spacing for better visual organization of the buttons.

src/app/(mobile-ui)/layout.tsx (2)

24-25: LGTM! Clear documentation and correct regex update.

The comment clearly explains the purpose of public paths, and the regex is correctly updated to include /support while maintaining the existing patterns.

---

84-87: LGTM! Consistent public path handling.

The public path logic is properly implemented and consistently used in the authentication gating condition. The isPublicPath variable correctly utilizes the updated regex pattern.