sojorn/sojorn_app/lib/providers/onboarding_provider.dart
Patrick Britton 3c4680bdd7 Initial commit: Complete threaded conversation system with inline replies
**Major Features Added:**
- **Inline Reply System**: Replace compose screen with inline reply boxes
- **Thread Navigation**: Parent/child navigation with jump functionality
- **Chain Flow UI**: Reply counts, expand/collapse animations, visual hierarchy
- **Enhanced Animations**: Smooth transitions, hover effects, micro-interactions

 **Frontend Changes:**
- **ThreadedCommentWidget**: Complete rewrite with animations and navigation
- **ThreadNode Model**: Added parent references and descendant counting
- **ThreadedConversationScreen**: Integrated navigation handlers
- **PostDetailScreen**: Replaced with threaded conversation view
- **ComposeScreen**: Added reply indicators and context
- **PostActions**: Fixed visibility checks for chain buttons

 **Backend Changes:**
- **API Route**: Added /posts/:id/thread endpoint
- **Post Repository**: Include allow_chain and visibility fields in feed
- **Thread Handler**: Support for fetching post chains

 **UI/UX Improvements:**
- **Reply Context**: Clear indication when replying to specific posts
- **Character Counting**: 500 character limit with live counter
- **Visual Hierarchy**: Depth-based indentation and styling
- **Smooth Animations**: SizeTransition, FadeTransition, hover states
- **Chain Navigation**: Parent/child buttons with visual feedback

 **Technical Enhancements:**
- **Animation Controllers**: Proper lifecycle management
- **State Management**: Clean separation of concerns
- **Navigation Callbacks**: Reusable navigation system
- **Error Handling**: Graceful fallbacks and user feedback

This creates a Reddit-style threaded conversation experience with smooth
animations, inline replies, and intuitive navigation between posts in a chain.
2026-01-30 07:40:19 -06:00

41 lines
1.3 KiB
Dart

import 'package:flutter_riverpod/flutter_riverpod.dart';
import 'api_provider.dart';
import 'auth_provider.dart';
/// Whether onboarding is complete.
/// We now trust the backend `has_completed_onboarding` flag to avoid web
/// storage inconsistencies that can trap users on the interests screen.
final profileExistsProvider = FutureProvider.autoDispose<bool>((ref) async {
final authenticated = ref.watch(isAuthenticatedProvider);
if (!authenticated) return false;
final api = ref.read(apiServiceProvider);
final authService = ref.read(authServiceProvider);
try {
final data = await api.getProfile(); // /profile GET
final profile = data['profile'];
final hasCompleted = profile.hasCompletedOnboarding;
// Keep local cache in sync for faster subsequent boots.
if (hasCompleted) {
await authService.markOnboardingCompleteLocally();
}
return hasCompleted;
} catch (_) {
// Fallback to local cache if network fails.
return authService.isOnboardingComplete();
}
});
/// Whether the current user has selected at least one category
final categorySelectionProvider = FutureProvider.autoDispose<bool>((ref) async {
final authenticated = ref.watch(isAuthenticatedProvider);
if (!authenticated) {
return false;
}
final apiService = ref.watch(apiServiceProvider);
return apiService.hasCategorySelection();
});