sojorn/_legacy/supabase/migrations/20260118_follow_notifications.sql
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

68 lines
1.9 KiB
PL/PgSQL

-- Follow notifications: trigger + metadata
alter table if exists notifications
add column if not exists metadata jsonb not null default '{}'::jsonb;
do $$
begin
alter type notification_type add value if not exists 'follow_request';
alter type notification_type add value if not exists 'new_follower';
alter type notification_type add value if not exists 'request_accepted';
end $$;
create or replace function handle_follow_notification()
returns trigger
language plpgsql
as $$
begin
if tg_op = 'INSERT' then
if new.status = 'pending' then
insert into notifications (user_id, type, actor_id, metadata)
values (
new.following_id,
'follow_request',
new.follower_id,
jsonb_build_object(
'follower_id', new.follower_id,
'following_id', new.following_id,
'status', new.status
)
);
elsif new.status = 'accepted' then
insert into notifications (user_id, type, actor_id, metadata)
values (
new.following_id,
'new_follower',
new.follower_id,
jsonb_build_object(
'follower_id', new.follower_id,
'following_id', new.following_id,
'status', new.status
)
);
end if;
elsif tg_op = 'UPDATE' then
if old.status = 'pending' and new.status = 'accepted' then
insert into notifications (user_id, type, actor_id, metadata)
values (
new.follower_id,
'request_accepted',
new.following_id,
jsonb_build_object(
'follower_id', new.follower_id,
'following_id', new.following_id,
'status', new.status
)
);
end if;
end if;
return new;
end;
$$;
drop trigger if exists follow_notification_trigger on follows;
create trigger follow_notification_trigger
after insert or update on follows
for each row execute function handle_follow_notification();