pezkuwichain/pwap
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pwap.git synced 2026-04-23 01:17:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
63 Commits 1 Branch 0 Tags
8c69b4e5b2022ed8fb94d1f3d2355af802016fa2
Commit Graph

5 Commits

Author SHA1 Message Date
pezkuwichain 02f5718211 fix: Use SECURITY DEFINER function for profile upserts 
Changes:
1. Created migration 004_create_upsert_function.sql:
   - Creates upsert_user_profile() function with SECURITY DEFINER
   - Bypasses RLS to allow profile creation/updates
   - Only accessible to authenticated users via auth.uid()

2. Updated ProfileSettings.tsx:
   - Changed from direct upsert to RPC function call
   - Updated updateProfile() to use supabase.rpc()
   - Updated updateNotificationSettings() to use same function

This solves the RLS policy violation by using a secure
server-side function that properly handles authentication.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-29 05:10:53 +03:00
pezkuwichain 2e33e84c7c fix: Simplify profile RLS policies to allow insert 
Updated migration 003 to properly handle RLS:
- Make username nullable with default
- Drop all existing policies and recreate them
- Add proper INSERT policy with WITH CHECK clause
- Add UPDATE policy with both USING and WITH CHECK

This fixes RLS error blocking profile creation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-29 05:07:18 +03:00
pezkuwichain c9939ee656 fix: Use upsert for profile updates to handle missing rows 
Changes:
1. Created migration 003_fix_profile_creation.sql:
   - Added INSERT policy for profiles table
   - Made username nullable with default value
   - Created upsert_profile function for safe upserts

2. Updated ProfileSettings.tsx:
   - Changed from .update() to .upsert()
   - Added id field to upsert data
   - Added loadProfile() call after save to refresh state

This fixes the issue where users couldn't update their profile
because no profile row existed in the database.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-29 04:45:23 +03:00
pezkuwichain ba27543274 feat: Add missing columns to profiles table 
Added comprehensive user profile columns to fix 400 Bad Request errors:

Profile Information:
- bio, phone, location, website
- phone_number, recovery_email, recovery_email_verified

User Preferences:
- language (default: 'en')
- theme (default: 'dark')

Notification Settings:
- notifications_email (default: true)
- notifications_push (default: false)
- notifications_sms (default: false)

Security:
- two_factor_enabled (default: false)
- email_verified (for compatibility)

Metadata:
- joined_at (synced from created_at)
- role (default: 'Member')

Indexes:
- Created indexes on phone, language, location for faster queries

This resolves 400 errors when updating profile settings.

Migration Status: ✅ Successfully executed on Supabase

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-29 04:13:58 +03:00
pezkuwichain 768034a91f fix: Configure Supabase and add database schema for sign up 
- Update VITE_SUPABASE_URL to correct API endpoint
- Update .env.example with correct Supabase project URL
- Add comprehensive database migration script (001_initial_schema.sql)
- Create profiles, admin_roles, wallets, and referral_history tables
- Implement Row Level Security (RLS) on all tables
- Add auto-generation of referral codes
- Add detailed Supabase setup guide (README.md)

This fixes the sign up issue by:
1. Correcting invalid Supabase credentials format
2. Providing SQL schema for required database tables
3. Setting up proper RLS policies for data security

To complete setup:
1. Run supabase/migrations/001_initial_schema.sql in Supabase SQL Editor
2. Add real VITE_SUPABASE_ANON_KEY to .env file
3. Test sign up functionality

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-28 22:19:22 +03:00