93040a0684
Three related UX fixes on the client. 1. Participants count on profile DMs always have exactly two participants (you and the contact) so a "Участников: 1" row was confusing — either it's obviously the other person or it's wrong depending on how you count. Removed for direct conversations; the row still appears for group chats (and shows an em-dash until v2.1.0 gives groups a real member list). 2. Dev feed seed now activates on network / 404 errors The seed was only surfaced when the real API returned an EMPTY array. If the node was down (Network request failed) or the endpoint replied 404, the catch block quietly set posts to [] and the list stayed blank — defeating the point of the seed. Now both the empty- response path AND the network-error path fall back to getDevSeedFeed(), so scrolling / like-toggling works even without a running node. Also made the __DEV__ lookup more defensive: use `globalThis.__DEV__` at runtime instead of the typed global. Some bundler configurations have the TS type but not the runtime binding, or vice-versa — the runtime lookup always agrees with Metro. 3. Back from profile → previous screen instead of tab root Root cause: AnimatedSlot rendered <Slot>, which is stack-less. When /chats/xyz pushed /profile/abc (cross-group), the chats group unmounted. Hitting Back then re-entered chats at its root (/chats list) rather than /chats/xyz. Replaced <Slot> with <Stack> in AnimatedSlot. Tab switching still stays flat because NavBar uses router.replace (which maps to navigation.replace on the Stack — no history accumulation). Cross-group pushes (post author tap from feed, avatar tap from chat header, compose modal) now live in the outer Stack's history, so Back pops correctly to the caller. The nested Stacks (chats/_layout.tsx, feed/_layout.tsx, profile/_layout.tsx) still handle intra-group navigation as before. The PanResponder-based swipe-right-to-back was removed since the native Stack now provides iOS edge-swipe natively; Android uses the system back button. animation: 'none' keeps the visual swap instant — matches the prior Slot look so nothing flashes slide-animations that weren't there before. Sub-group layouts can opt into slide_from_right themselves (profile/_layout.tsx and feed/_layout.tsx already do). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
36 lines
1.3 KiB
TypeScript
36 lines
1.3 KiB
TypeScript
/**
|
|
* AnimatedSlot — renders the (app) group as a native <Stack>.
|
|
*
|
|
* Why Stack instead of Slot: Slot is stack-less. When a child route
|
|
* (e.g. profile/[address]) pushes another child, Slot swaps content
|
|
* with no history, so router.back() falls all the way through to the
|
|
* URL root instead of returning to the caller (e.g. /chats/xyz →
|
|
* /profile/abc → back should go to /chats/xyz, not to /chats).
|
|
*
|
|
* Tab switching stays flat because NavBar uses router.replace, which
|
|
* maps to navigation.replace on the Stack → no history accumulation.
|
|
*
|
|
* animation: 'none' on tab roots keeps tab-swap instant (matches the
|
|
* prior Slot look). Sub-routes (profile/*, compose, feed/*, chats/[id])
|
|
* inherit slide_from_right from their own nested _layout.tsx Stacks,
|
|
* which is where the push animation happens.
|
|
*
|
|
* This file is named AnimatedSlot for git-history continuity — the
|
|
* Animated.Value + translateX slide was removed earlier (got stuck at
|
|
* ±width when interrupted by re-render cascades).
|
|
*/
|
|
import React from 'react';
|
|
import { Stack } from 'expo-router';
|
|
|
|
export function AnimatedSlot() {
|
|
return (
|
|
<Stack
|
|
screenOptions={{
|
|
headerShown: false,
|
|
contentStyle: { backgroundColor: '#000000' },
|
|
animation: 'none',
|
|
}}
|
|
/>
|
|
);
|
|
}
|