@t0maboro/split stack columns poc

[t0maboro]

Test with TestSplitStackColumns. I'm dumping all commits from PoC based on the RFC https://github.com/software-mansion/react-native-screens-labs/pull/1805 (option B). The plan is to create a single PR for each commit from here.

---

A Split column becomes a navigation stack of screens with Stack v5 semantics. Nothing between Split.Host and the screens is a React view, so the problem of hanging views from #4602 doesn't happen.
Proposed API for this option:

<Split.Host>
  <Split.Column>
    <Split.Stack>
      {screens.map(screen => (
        <Split.Screen
          key={screen.key}
          screenKey={screen.key}
          activityMode={screen.activityMode}
          onDismiss={() => remove(screen.key)}>
          <Split.HeaderConfig title={screen.key} />
          <Content />
        </Split.Screen>
      ))}
    </Split.Stack>
  </Split.Column>
  <Split.Column>{/* plain one-screen column, as today */}</Split.Column>
</Split.Host>

One commit per step, in the order of the RFC's implementation plan:

1. and 2. Already on landed on main
2. ios/stack/header moves to ios/header, RNSStackHeader* becomes RNSHeader*. Android header should be aligned.
3. Stack core logic lifted out of Stack.Host and typed on RNSStackScreenProviding.
4. Header coordinator works on any UIViewController; the header config resolves its screen through the protocol instead of asserting on the Stack screen class.
   6 RNSSplitColumnController (manager, not VC), a native object with no React counterpart which owns the column's navigation controller and its frame observer and replaces RNSSplitNavigationController.
5. A Split.Column with a Split.Stack child renders no native view and only provides its column id through context; the host routes each mounted screen to its column; the column controller drives RNSStackOperationCoordinator over UIView<RNSStackScreenProviding> the way Stack.Host does.
6. Split.HeaderConfig renders the neutral header config; RNSHeaderCoordinator owned by RNSSplitScreenController applies it to the column's navigation item.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}