-
Notifications
You must be signed in to change notification settings - Fork 2
Feature/zenith hall transformation #231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Fix update_username function to use proper schema references (public.profiles) - Add comprehensive database migration for profiles table and functions - Improve error handling in UsernameField component for database issues - Add database diagnostic and testing SQL scripts Fixes: relation 'profiles' does not exist error in username updates Resolves: Username update functionality not working due to missing schema references
…e-function Fix: Resolve username update database function error
…n improvements 🚀 Major Features Added: - Complete events management system with registration and payment - Master registration system for unified user tracking - Enhanced admin dashboard with events management - Improved user profile and dashboard functionality 🐛 Database Fixes: - Fixed username update function schema references (public.profiles) - Resolved 'relation profiles does not exist' error - Added comprehensive database migration and diagnostic tools 📁 New API Endpoints: - /api/events/* - Complete events CRUD operations - /api/events/[slug]/register - Event registration with payment - /api/events/[slug]/payment - Payment processing for events - /api/registrations/* - Master registration system - /api/user/events/* - User-specific event data - /api/register - User registration endpoint 🎨 New Pages & Components: - /events - Public events listing page - /events/[slug] - Individual event pages with registration - /protected/events - User's registered events - /protected/hackathons - Enhanced hackathons page - Enhanced admin events management interface 🔧 Services & Hooks: - useEvents - Events data management hook - useEventRegistrations - Event registration management - useMasterRegistrations - Master registration system - events.ts - Events service layer - master-registrations.ts - Registration service layer 📊 Admin Improvements: - Enhanced events management in admin panel - Improved dashboard content and user experience - Better webhook handling for payments 🛠️ Technical Improvements: - TypeScript types for events system - Improved error handling and validation - Better database schema and function management - Enhanced security and permissions This comprehensive update includes all recent development work including the critical database function fix for username updates.
…es-and-fixes 🚀 Comprehensive Updates: Events System, Database Fixes & Admin Improvements
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. WalkthroughAdds a full events system: admin CRUD UI and service-role API; public events APIs with caching; user registration flows (free and paid via Razorpay) with related pages and hooks; master registrations service and user-facing dashboards; Razorpay webhook enhancements; type definitions; multiple SQL migrations/utilities for profiles and username functions; minor UI/component tweaks. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor U as User
participant P as Event Register Page (/events/[slug]/register)
participant API as /api/events/[slug]/payment (POST)
participant RZ as Razorpay
participant V as /api/events/[slug]/payment (PUT)
participant S as Supabase+DB
U->>P: Click "Pay & Register"
P->>API: Create order (POST)
API->>S: Validate user/event, capacity, pending
S-->>API: OK + order record
API-->>P: { orderId, key, amount, notes }
P->>RZ: Open Checkout (orderId)
RZ-->>P: payment_id + signature
P->>V: Verify (PUT)
V->>S: Verify pending, update registration, mark paid
S-->>V: Updated
V-->>P: success: true
P-->>U: Show success and redirect
sequenceDiagram
autonumber
actor U as User
participant P as Event Page (/events/[slug])
participant API as /api/events/[slug]/register (POST/DELETE)
participant S as Supabase+DB
U->>P: Click "Register" (free)
P->>API: POST register
API->>S: Auth, capacity, isRegistered?
S-->>API: Insert registration, inc count
API-->>P: success
P-->>U: Status updated
U->>P: Click "Unregister"
P->>API: DELETE unregister
API->>S: Delete registration, dec count
API-->>P: success
P-->>U: Status updated
sequenceDiagram
autonumber
participant C as Client
participant E as /api/events (GET)
participant Cache as UnifiedCache
participant Svc as eventsService
participant DB as Supabase
C->>E: GET with filters
E->>Cache: Read key(filters)
alt Cache hit
Cache-->>E: Cached response
E-->>C: Return cached
else Cache miss
E->>Svc: getEvents(filters)
Svc->>DB: Query with filters + count
DB-->>Svc: rows, total
Svc-->>E: { events, total, hasMore }
E->>Cache: Write key(filters)
E-->>C: Return fresh
end
Estimated code review effort🎯 5 (Critical) | ⏱️ ~120 minutes Poem
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.
Please see the documentation for more information. 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 detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (32)
✨ Finishing touches
🧪 Generate unit tests
Comment |
Summary by CodeRabbit