feat: replace numeric user ID in shareable profile URL with name slug

[Sachinchaurasiya360]

Feature Request / Bug

Route: /student/profile/public/:id
Example URL: https://www.internhack.xyz/student/profile/public/1

Problem

The shareable profile URL currently uses the numeric user ID (e.g. /public/1). This is:

• Not user-friendly or shareable in a professional context
• Exposes internal database IDs
• Hard to remember or share verbally

Proposed Solution

Replace the numeric ID in the URL with a URL-safe version of the user's name or a unique username slug.

Option A — Name slug (e.g. /public/sachin-chaurasiya):

• Generate a URL-safe slug from user.name (lowercase, spaces to hyphens)
• Add a profileSlug field to the user table with a unique index
• Fall back to name-id (e.g. sachin-chaurasiya-42) if the name slug is already taken

Option B — Username field:

• Add a username field that students can set manually from their profile settings
• Validate uniqueness and URL safety on save

Acceptance Criteria

• The shareable URL shows a human-readable identifier instead of a numeric ID
• Old numeric-ID URLs either redirect to the new slug URL or continue to work
• The copy URL button in StudentProfilePage.tsx generates the slug-based URL
• Profile slug is unique across all users

[Rajal-ui]

Hi @Sachinchaurasiya360,I'd love to work on this issue.

Approach

Implementing Option A (auto-generated name slug with numeric fallback) — no extra user input required, immediate improvement.

Backend

1. Add profileSlug String? @unique to user model in schema.prisma
   Run prisma migrate dev --name add_profile_slug_to_user

2. Add generateSlug utility:

   • Lowercase name, replace spaces with hyphens, strip non-alphanumeric chars except hyphens
   • Check uniqueness: if "sachin-chaurasiya" taken, try "sachin-chaurasiya-42" (append userId)
   • This guarantees uniqueness without extra DB queries

3. On user registration/profile update: generate and save profileSlug if not already set — add to auth.service.ts
   createUser and updateProfile methods

4. Backfill existing users: add a one-time migration script that generates profileSlug for all users where it is null

5. Update GET /auth/profile/:id to also accept slug:
   Try parsing param as integer first (numeric ID backward compat)
   If not a number, query by profileSlug instead Old numeric URLs continue working — no redirects needed

Frontend

6. In StudentProfilePage.tsx, update the copy URL button:
   Use profile.profileSlug if available, fall back to user.id
   URL: /student/profile/public/{profileSlug ?? id}

7. Update PublicProfilePage.tsx route param handling to pass
   slug or id to the API — no change needed if backend handles both

Outcome

• New URLs: /student/profile/public/sachin-chaurasiya
• Old URLs: /student/profile/public/42 still work
• Slug auto-generated on registration, no user action needed
• Unique guaranteed via name + userId fallback pattern
• No redirect needed — backend accepts both formats

Files to Change

server/src/database/prisma/schema/base.prisma
server/src/module/auth/auth.service.ts
server/src/module/auth/auth.routes.ts
client/src/module/student/profile/StudentProfilePage.tsx

Happy to open a PR if assigned. Thank you!