feat(showroom): Database schema and public routing

[rushikesh-bobade]

🚀 Problem Statement

FlipTrack is currently just an internal management tool. We want to empower our users to actually sell their inventory directly by offering them a public "Showroom" profile.

🛠️ Proposed Solution

We need to lay the backend groundwork for Public Showrooms. This involves updating the database schema to support public visibility and creating the dynamic routing structure.

✅ Acceptance Criteria

• Update prisma/schema.prisma: Add a unique username field to the User model, and an isPublic boolean flag to the InventoryItem model.
• Create the database migration (npx prisma migrate dev).
• Create a new dynamic route app/routes/$username.tsx that fetches only the isPublic = true inventory items for the given user.
• Ensure the loader securely strips out sensitive financial data (like purchasePrice) before returning the data to the client.

[mrunmayeekokitkar]

Hi! I'd like to work on this issue. Could you please assign it to me?

[github-actions]

Hi @mrunmayeekokitkar! 👋

Thank you for your interest in contributing to this repository! Please wait until a maintainer officially assigns you to this issue before opening a Pull Request.

While you wait, please consider starring ⭐ this repository to show your support! We review requests regularly and will assign it as soon as possible if it's available. Happy coding! 🚀

[rushikesh-bobade]

@mrunmayeekokitkar Thanks for volunteering for this one too!

Since you were just assigned to Issue #90, we ask that you finish and merge that PR first. To keep things fair for everyone during ECSoC, we limit contributors to one active issue at a time.

Once your first PR is merged, let me know. If this is still open, it's all yours!

[Yuva-Deekshitha-N]

Hi! I'd like to work on this issue. It looks like an interesting backend feature involving Prisma schema updates, migrations, and implementing the dynamic public showroom route while ensuring sensitive data is excluded from the loader response.

Could you please assign it to me? Thanks!

[rushikesh-bobade]

@Yuva-Deekshitha-N Hey! I will gladly hold this one for you and assign it to you as promised. However, to keep things fair with our event rules, I can't officially assign it to you until your current PR (#51) gets merged.

Just wrap up those merge conflicts, and the second that PR is merged, I'll officially assign this one to you!

[Yuva-Deekshitha-N]

Hi @rushikesh-bobade ! Now, could you please assign it to me?

[karrisanthoshigayatri]

Hi @rushikesh-bobade ,

I noticed this issue is already assigned, so I don't want to duplicate the work.

If it becomes available or if any follow-up improvements are needed after the current implementation, I'd be happy to contribute. Thanks!