sojorn/sojorn_docs/legacy/LINKS_FIX.md
Patrick Britton 38653f5854 Sojorn Backend Finalization & Cleanup - Complete Migration from Supabase
##  Phase 1: Critical Feature Completion (Beacon Voting)
- Add VouchBeacon, ReportBeacon, RemoveBeaconVote methods to PostRepository
- Implement beacon voting HTTP handlers with confidence score calculations
- Register new beacon routes: /beacons/:id/vouch, /beacons/:id/report, /beacons/:id/vouch (DELETE)
- Auto-flag beacons at 5+ reports, confidence scoring (0.5 base + 0.1 per vouch)

##  Phase 2: Feed Logic & Post Distribution Integrity
- Verify unified feed logic supports all content types (Standard, Quips, Beacons)
- Ensure proper distribution: Profile Feed + Main/Home Feed for followers
- Beacon Map integration for location-based content
- Video content filtering for Quips feed

##  Phase 3: The Notification System
- Create comprehensive NotificationService with FCM integration
- Add CreateNotification method to NotificationRepository
- Implement smart deep linking: beacon_map, quip_feed, main_feed
- Trigger notifications for beacon interactions and cross-post comments
- Push notification logic with proper content type detection

##  Phase 4: The Great Supabase Purge
- Delete function_proxy.go and remove /functions/:name route
- Remove SupabaseURL, SupabaseKey from config.go
- Remove SupabaseID field from User model
- Clean all Supabase imports and dependencies
- Sanitize codebase of legacy Supabase references

##  Phase 5: Flutter Frontend Integration
- Implement vouchBeacon(), reportBeacon(), removeBeaconVote() in ApiService
- Replace TODO delay in video_comments_sheet.dart with actual publishComment call
- Fix compilation errors (named parameters, orphaned child properties)
- Complete frontend integration with Go API endpoints

##  Additional Improvements
- Fix compilation errors in threaded_comment_widget.dart (orphaned child property)
- Update video_comments_sheet.dart to use proper named parameters
- Comprehensive error handling and validation
- Production-ready notification system with deep linking

##  Migration Status: 100% Complete
- Backend: Fully migrated from Supabase to custom Go/Gin API
- Frontend: Integrated with new Go endpoints
- Notifications: Complete FCM integration with smart routing
- Database: Clean of all Supabase dependencies
- Features: All functionality preserved and enhanced

Ready for VPS deployment and production testing!
2026-01-30 09:24:31 -06:00

25 lines
2.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Links Fix Profile Deep Link Bug
## Issue
- Clicking any user profile link (e.g., from a post, notification, or shared URL) always opened the current users profile instead of the target profile.
- Root cause: GoRouter tab shell state was local to `HomeShell` (an `IndexedStack` driven by `_currentIndex`), so `context.go('/u/<handle>')` left the UI stuck on the “Profile” tab (current user view) even when the route was for another user.
- Backend `GetProfile` endpoint only returned full profile data by user ID; when the app requested by handle it fell back to the signedin user, reinforcing the wrong profile display.
## Fix
- Frontend routing:
- Replaced manual `IndexedStack` shell with GoRouter `StatefulShellRoute.indexedStack`; tab index now follows router state.
- `/profile` (current user) is a shell branch; `/u/:username` is a separate root route that renders `ViewableProfileScreen` so it no longer competes with the shell tab.
- `HomeShell` now uses the GoRouter navigation shell (no local `_currentIndex`) and passes branch index to quips for playback pausing.
- `ViewableProfileScreen` ownership check now compares both authenticated user id and handle against the requested handle.
- Backend:
- `GetProfile` now accepts `?handle=<username>` and resolves in order: handle → :id → auth user.
- `GetProfileByHandle` returns full profile fields (id, handle, display_name, bio, avatar_url, origin_country, onboarding flag, created_at) so clients can render the viewed user.
## Files Touched
- Frontend: `lib/routes/app_routes.dart`, `lib/screens/home/home_shell.dart`, `lib/screens/auth/auth_gate.dart`, `lib/screens/auth/category_select_screen.dart`, `lib/screens/quips/feed/quips_feed_screen.dart`, `lib/screens/profile/viewable_profile_screen.dart`.
- Backend: `internal/handlers/user_handler.go`, `internal/repository/user_repository.go`.
## Deployment Notes
- Backend binary rebuilt at `/opt/sojorn/go-backend/bin/sojorn-api` (tests pass). Needs sudo to copy over `/opt/sojorn/bin/sojorn-api` and restart `sojorn-api.service`.
- Frontend changes live in the local workspace; rebuild/deploy the app to pick up the routing fix.