refactor(dashboard): extract PROFILE_URL helper from ShareSheet into utils/urls.ts

[JhaSourav07]

🧩 Background

PROFILE_URL in components/dashboard/ShareSheet.tsx is a function that builds the dashboard URL. This URL format is likely needed in other places (og route, landing page, etc.) and should be centralized.

🎯 Objective

Move PROFILE_URL to utils/urls.ts and import from there.

📁 Files to touch

• utils/urls.ts (new)
• components/dashboard/ShareSheet.tsx

🛠️ Implementation steps

• Create getDashboardUrl(username: string): string using window.location.origin with an SSR fallback.
• Import and use in ShareSheet.
• Add a unit test.

✅ Definition of done

• URL helper is in one place.
• All ShareSheet tests pass.

[nivedha2025cse-gif]

hi @JhaSourav07 kindly assign this to me

[soumyasekharshee265-ux]

Hi @JhaSourav07! 👋

I'd love to take up this issue and refactor the PROFILE_URL logic into a centralized URL helper. This is a clean, well-scoped refactor that will improve maintainability and prevent URL duplication across the codebase (og routes, landing page, ShareSheet, etc.) — and I'm confident I can ship it cleanly.

Why I'm a good fit for this issue

• ✅ I've carefully read the issue and understand the exact scope — extracting PROFILE_URL from components/dashboard/ShareSheet.tsx into a new utils/urls.ts helper as getDashboardUrl(username).
• ✅ I'm comfortable with the project's stack — Next.js, TypeScript, TailwindCSS, and I'm familiar with Next.js SSR considerations (which is critical here since window.location.origin isn't available during server-side rendering).
• ✅ I understand how to properly handle the SSR fallback — using an env var like NEXT_PUBLIC_APP_URL or process.env.VERCEL_URL as a safe default when typeof window === 'undefined'.
• ✅ I've written similar URL/utility helpers in previous Next.js projects and know how to write clean unit tests for them using the existing test setup (vitest based on vitest.config.ts in the repo).

My plan of action

1. Create utils/urls.ts exporting a typed helper:

   export function getDashboardUrl(username: string): string

   • Uses window.location.origin on the client.
   • Falls back to process.env.NEXT_PUBLIC_APP_URL (or sensible default) during SSR.
2. Refactor components/dashboard/ShareSheet.tsx to import and use getDashboardUrl() instead of the inline PROFILE_URL logic.
3. Add a unit test in the appropriate __tests__/ location covering:
   • Correct URL generation on the client.
   • Correct fallback behavior during SSR.
   • Edge cases (empty username, special characters).
4. Verify all existing ShareSheet tests still pass.
5. Run lint, type-check, and the full test suite before opening the PR.
6. Submit a clean PR with a clear description and link back to this issue.

Definition of done checklist

• ✅ URL helper lives in one place (utils/urls.ts)
• ✅ All ShareSheet tests pass
• ✅ New unit test added for getDashboardUrl

Estimated timeline

I can submit a PR within 1–2 days of being assigned.

---

Since this issue is labeled GSSoC 2026, good first issue, and refactor, and it's a self-contained, well-scoped task with a clear definition of done, I'd really appreciate the opportunity to work on it. Could you please assign this to me under GSSoC 2026? 🙌

Thank you!

[JhaSourav07]

/assign @nivedha2025cse-gif

[github-actions]

✅ Successfully assigned issue to @nivedha2025cse-gif

💡 Please read CONTRIBUTING.md if you haven't already. Good luck! 🚀

[akshayad2006-cmd]

Hi @JhaSourav07 ,
I would like to work on this issue under GSSoC 2026.
I can help centralize the PROFILE_URL logic by moving it into a reusable utility helper, update ShareSheet.tsx to use it, and add the required unit test while ensuring all existing tests continue to pass.
Please assign this issue to me.

[github-actions]

👋 Hey @akshayad2006-cmd! Looks like you want to work on this issue — awesome! 🎉

We don't assign issues through comments like this. Here's how our system works:

🤖 How to Claim an Issue

Comment /claim on this issue and our bot will automatically assign it to you (if you're eligible).

/claim

📋 A Few Things to Know

• You can hold a maximum of 3 open issues at a time.
• If there's no activity for 3 days, the assignment will automatically expire so others can pick it up.
• Make sure to read our CONTRIBUTING.md before you start — it covers code style, commit conventions, and the PR checklist.

💬 Join Our Discord

Get faster help, collaborate with other contributors, and stay updated with project news:

Happy contributing! 🚀

[akshayad2006-cmd]

Hi @JhaSourav07 ,
I would like to work on this issue under GSSoC 2026.
I can help centralize the PROFILE_URL logic by moving it into a reusable utility helper, update ShareSheet.tsx to use it, and add the required unit test while ensuring all existing tests continue to pass.
Please assign this issue to me.
/claim

[github-actions]

❌ This issue is already assigned to @nivedha2025cse-gif