Feat/guests page mobile

[manueltorres0]

Description

• added the guests page for mobile
• used hardcoded data and filtering mechanism
• added many reusable custom components, such as Box, Dropdown, etc.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (code improvement without changing functionality)
• Documentation update
• Configuration/infrastructure change
• Performance improvement
• Test coverage improvement

Related Issue(s)

Related to #103

What Changed?

• added guest list tab on mobile
• added reusable ui components on mobile
• changed the babel config because it was messing with the expo router: removed the env react plugin because
  expo should expose it

Testing & Validation

How this was tested

Tested visually with the frontend

Screenshots/Recordings

demo

Unfinished Work & Known Issues

• None, this PR is complete and production-ready
• The following items are intentionally deferred:
  • *** I still have to make the individual guest profile page

Pre-Merge Checklist

Code Quality

• Code follows the project's style guidelines and conventions
• Self-review completed (I've reviewed my own code for obvious issues)
• No debugging code, console logs, or commented-out code left behind
• No merge conflicts with the base branch
• Meaningful commit messages that explain the "why"

Testing & CI

• All CI checks are passing
• All new and existing tests pass locally
• Test coverage hasn't decreased (or decrease is justified)
• Linting passes without errors

Documentation

• Code is self-documenting or includes helpful comments for complex logic
• API documentation updated (if backend endpoints changed)
• Type definitions are accurate and up-to-date

Reviewer Notes

• Areas needing extra attention: ...
• Questions for reviewers: ...

[Dao-Ho]

Fire ship!! 🔥 Just one smol nit on the class merges/fusion

[Dao-Ho]

since this is temporary, I'd be make a global const for the file rather than embedding it in the function itself.

const FILTER_CONFIG

[Dao-Ho]

we shouldn't need || '' to default every time we have an optional className parameter

I would implement a utils cn function for you to merge classNames (would be very useful for future class merges/fusion as well

import { clsx, type ClassValue } from "clsx";
import { twMerge } from "tailwind-merge";

export function cn(...inputs: ClassValue[]) {
  return twMerge(clsx(inputs));
}

call ex.

className={cn(
  'flex-row items-center p-[3vw] border border-gray-300 rounded-md active:bg-gray-100',
  className
)}