Package
@effector/router-react-native
What happened?
The navigator configuration accepts RouteView objects from @effector/router-react, and RouteView supports nested children for Outlet rendering. However, both navigators pass routeView.view directly to Stack.Screen or Tab.Screen without providing the OutletContext or rendering routeView.children.
A parent RouteView with an active nested child therefore renders without its child content in React Native.
Reproduction
- Create a parent RouteView with children containing a child RouteView.
- Render Outlet from the parent view.
- Register the parent view in createStackNavigator or createBottomTabsNavigator.
- Open the child route.
Expected: Outlet renders the active nested child view, matching createRoutesView behavior.
Actual: the navigator bypasses createRoutesView and Outlet receives no nested RouteView context, so the child view is not rendered.
Environment
- @effector/router-react-native: 1.0.1
- @effector/router-react: 1.0.1
- @effector/router: 1.1.1
- effector: >=23
- React: 18 or 19
- React Native: >=0.70
- Node.js: 24.x
Logs / screenshots
Not applicable; this is a deterministic nested RouteView contract issue.
Package
@effector/router-react-native
What happened?
The navigator configuration accepts RouteView objects from @effector/router-react, and RouteView supports nested children for Outlet rendering. However, both navigators pass routeView.view directly to Stack.Screen or Tab.Screen without providing the OutletContext or rendering routeView.children.
A parent RouteView with an active nested child therefore renders without its child content in React Native.
Reproduction
Expected: Outlet renders the active nested child view, matching createRoutesView behavior.
Actual: the navigator bypasses createRoutesView and Outlet receives no nested RouteView context, so the child view is not rendered.
Environment
Logs / screenshots
Not applicable; this is a deterministic nested RouteView contract issue.