refactor(Tabs): Split JS components and specs internally by t0maboro · Pull Request #3722 · software-mansion/react-native-screens

t0maboro · 2026-03-04T11:17:06Z

Important notes before reviewing this PR:

Please get familiar with this RFC-994 as an introcution why we're refactoring this code.
There will be 2 follow-up PRs:
- PR in which I'll rename props to align with https://github.com/software-mansion/react-native-screens-labs/pull/1023 , so in this PR the only rename that I will accept is standardAppearanceAndroid -> standardAppearance
- PR for organizing files under specific directories (host, screen, accesory directories)

Description

This PR introduces a platform separation for the TabsHost and TabsScreen components. The platform-specific code is now placed in a separate file for each platform.

From now on, platform-specific props should not be passed to the native side of components on other platforms. If a prop will have an empty implementation on the native side, it means that it was defined in the wrong location.

Caution

This is a breaking change to the public API.

Caution

Since we're no longer supporting old architecture, I didn't take any steps to synchronize these changes in it. In fact, the app most likely won't even build on Paper at this point.

Closes: https://github.com/software-mansion/react-native-screens-labs/issues/997
Closes: https://github.com/software-mansion/react-native-screens-labs/issues/998

Changes

From this PR:

Replaced TabsX.tsx with TabsX.ios.tsx and TabsX.android.tsx files.
Grouped platform-specific props into ios and android objects and created dedicated files for platform-specific props.
Moved shared logic into custom useTabsX hooks.
Added TS declaration files to satisfy typechecks, to allow importing components without platform extensions
Updated examples
From now on, we have 2 separate native components, each dedicated for a specific platform: RNSTabsHostAndroid & RNSTabsHostIOS (same approach for TabsScreen components)
All iOS-specific prop setters were removed from ViewManagers on Android.
RNSTabsHostShadowNode requires a platform-specific name - without that, app is crashing because the Host component hasn't been found in the registry.
All cpp enums and classes generated by codegen were updated for iOS conversions: react::RNSTabsScreenX -> react::RNSTabsScreenIOSX
componentNodeRef, which before this PR was present in shared code for TabsX component (via useTabsX hook) was moved to the component's implementation, because types have diverged between platforms after splitting native components
Props were reorganized and sorted in codegen Specs, to have clean separation between common and platform-specifc definitions.

Before & after - visual documentation

N/A - refactor, all behaviors should remain unchanged

Test plan

Go through all updated examples included in this PR

Checklist

Included code example that can be used to test this change.
Updated / created local changelog entries in relevant test files.
For visual changes, included screenshots / GIFs / recordings documenting the change.
For API changes, updated relevant public types.
Ensured that CI passes

Copilot

Pull request overview

This PR refactors the TabsHost/TabsScreen implementation to enforce platform separation (iOS vs Android) across JS components, TS types, and native/Fabric bindings, aligning with the RFC’s direction and making platform-specific props explicit.

Changes:

Split TabsHost / TabsScreen into platform-specific JS entrypoints (.ios.tsx / .android.tsx) and platform-specific Fabric codegen specs.
Reorganized the public TS API by moving platform-only props into ios / android nested objects and namespacing platform type exports.
Updated native iOS/Android registration and conversions to use platform-specific component names (e.g. RNSTabsHostIOS / RNSTabsHostAndroid) and adjusted example/test apps accordingly.

Reviewed changes

Copilot reviewed 47 out of 49 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/fabric/tabs/TabsScreenIOSNativeComponent.ts	iOS-only Fabric spec cleanup + renamed component to `RNSTabsScreenIOS`.
src/fabric/tabs/TabsScreenAndroidNativeComponent.ts	New Android-only Fabric spec (`RNSTabsScreenAndroid`).
src/fabric/tabs/TabsHostIOSNativeComponent.ts	iOS-only Fabric spec + renamed component to `RNSTabsHostIOS`.
src/fabric/tabs/TabsHostAndroidNativeComponent.ts	New Android-only Fabric spec (`RNSTabsHostAndroid`).
src/components/tabs/useTabsScreen.ts	Extracted shared TabsScreen lifecycle/debug logic into a hook.
src/components/tabs/useTabsHost.ts	Extracted shared TabsHost focus/debug logic into a hook.
src/components/tabs/index.ts	Exposes new namespaced platform type exports.
src/components/tabs/TabsScreen.types.ts	Moves platform props into `ios` / `android` sub-objects.
src/components/tabs/TabsScreen.tsx	Removed monolithic cross-platform implementation.
src/components/tabs/TabsScreen.ios.types.ts	New iOS-only TabsScreen types.
src/components/tabs/TabsScreen.android.types.ts	New Android-only TabsScreen types.
src/components/tabs/TabsScreen.ios.tsx	New iOS TabsScreen implementation wiring iOS-only props.
src/components/tabs/TabsScreen.android.tsx	New Android TabsScreen implementation wiring Android-only props.
src/components/tabs/TabsScreen.d.ts	TS shim for extensionless imports (`./TabsScreen`).
src/components/tabs/TabsHost.types.ts	Moves platform props into `ios` / `android` sub-objects.
src/components/tabs/TabsHost.tsx	Removed monolithic cross-platform implementation.
src/components/tabs/TabsHost.ios.types.ts	New iOS-only TabsHost types (incl. bottom accessory types).
src/components/tabs/TabsHost.android.types.ts	Placeholder Android-only TabsHost types.
src/components/tabs/TabsHost.ios.tsx	New iOS TabsHost implementation wiring iOS-only props + bottom accessory.
src/components/tabs/TabsHost.android.tsx	New Android TabsHost implementation.
src/components/tabs/TabsHost.d.ts	TS shim for extensionless imports (`./TabsHost`).
package.json	Updates iOS codegen component map to `RNSTabsHostIOS` / `RNSTabsScreenIOS`.
ios/tabs/screen/RNSTabsScreenEventEmitter.mm	Updates event emitter types for iOS-specific codegen symbols.
ios/tabs/screen/RNSTabsScreenEventEmitter.h	Header updates for iOS-specific event emitter types.
ios/tabs/screen/RNSTabsScreenComponentView.mm	Uses iOS-specific Props/EventEmitter/Descriptor types.
ios/tabs/host/RNSTabsHostEventEmitter.mm	Updates host event emitter type to iOS-specific codegen symbol.
ios/tabs/host/RNSTabsHostEventEmitter.h	Header updates for iOS-specific host event emitter type.
ios/tabs/host/RNSTabsHostComponentView.mm	Uses iOS-specific Props/EventEmitter types and enum names.
ios/conversion/RNSConversions.h	Updates conversion function signatures to iOS-specific codegen enums.
ios/conversion/RNSConversions-Tabs.mm	Updates conversion implementations to iOS-specific codegen enums.
common/cpp/react/renderer/components/rnscreens/RNSTabsHostShadowNode.h	Selects platform-specific Props/EventEmitter types via `#if !defined(ANDROID)`.
common/cpp/react/renderer/components/rnscreens/RNSTabsHostShadowNode.cpp	Makes host component name platform-specific (`RNSTabsHostIOS`/`Android`).
android/.../tabs/screen/TabsScreenViewManager.kt	Renames manager interface/delegate + module name to Android-specific.
android/.../tabs/host/TabsHostViewManager.kt	Renames manager interface/delegate + module name to Android-specific.
apps/src/tests/single-feature-tests/tabs/test-tabs-appearance-defined-by-selected-tab.tsx	Updates examples to use new `ios`/`android` prop nesting + namespaced types.
apps/src/tests/single-feature-tests/tabs/override-scroll-view-content-inset.tsx	Moves iOS-only prop under `tabScreenProps.ios`.
apps/src/tests/issue-tests/TestSafeAreaViewIOS/split-view/ConfigColumn.tsx	Updates icon props nesting for iOS.
apps/src/tests/issue-tests/TestSafeAreaViewIOS/bottom-tabs/BottomTabsComponent.tsx	Moves iOS-only props under `ios` and host props under `BottomTabsContainer.ios`.
apps/src/tests/issue-tests/TestHeaderHeight.tsx	Updates per-platform icon props nesting.
apps/src/tests/issue-tests/TestBottomTabsOrientation.tsx	Updates per-platform icon + orientation nesting.
apps/src/tests/issue-tests/TestBottomTabs/index.tsx	Updates appearance/icon props to new per-platform nesting.
apps/src/tests/issue-tests/Test3596.tsx	Updates icon nesting + formatting.
apps/src/tests/issue-tests/Test3443.tsx	Updates iOS icon nesting.
apps/src/tests/issue-tests/Test3342.tsx	Moves iOS-only props under `ios`.
apps/src/tests/issue-tests/Test3288.tsx	Moves iOS-only props (incl. bottom accessory) under `BottomTabsContainer.ios`.
apps/src/tests/issue-tests/Test3236.tsx	Moves controller mode under `BottomTabsContainer.ios`.
apps/src/tests/issue-tests/Test3212/StackInBottomTabsScenario.tsx	Moves scroll edge effects under `tabScreenProps.ios`.
apps/src/tests/issue-tests/Test3212/BottomTabsScenario.tsx	Moves scroll edge effects under `tabScreenProps.ios`.
apps/src/tests/issue-tests/Test3168.tsx	Moves iOS-only systemItem under `tabScreenProps.ios`.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/components/tabs/TabsHost.ios.types.ts

src/components/tabs/TabsHost.android.tsx

src/fabric/tabs/TabsHostAndroidNativeComponent.ts

Copilot

Pull request overview

Copilot reviewed 47 out of 49 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/fabric/tabs/TabsScreenAndroidNativeComponent.ts

kligarski

Looks great, I left only some minor nitpicks and suggestions.

One more question: what about bottom accessory: should it also have excludedPlatforms in spec file? Should the name be changed to TabsBottomAccessoryIOSNativeComponent or if this is already iOS-only component we don't need IOS part?

src/components/tabs/TabsHost.types.ts

src/components/tabs/TabsHost.android.tsx

src/components/tabs/TabsHost.ios.tsx

kligarski · 2026-03-04T14:51:41Z

src/components/tabs/TabsHost.ios.types.ts

+  /**
+   * @summary Specifies the color scheme used by the container and any child containers.
+   *
+   * The following values are currently supported:
+   * - `inherit` - the interface style from parent,
+   * - `light` - the light interface style,
+   * - `dark` - the dark interface style.
+   *
+   * @default inherit
+   *
+   * @platform ios
+   */
+  colorScheme?: TabsHostColorScheme;


This will be also available on Android soon but I'll move it in #3723 after we merge this PR.

Hmm, haven't we agree to lift all props planned for both platforms immediately up? https://github.com/software-mansion/react-native-screens-labs/discussions/1021#discussioncomment-15982501

If you put them here, then the PR with colorScheme support will block the stabilization. If you hoist it, then the colorScheme PR won't be blocking. I know that it's basically ready, but just from the organisational PoV.

What do you guys think?

Because we should be consistent for all such props

We just wanted this PR to be merged as quickly as possible and I didn't want to make @t0maboro rebase for the 100th time. For me it doesn't make any difference - it can be moved to shared now or later.

+1 ^
We may consider merging #3723 first if we want to have a final shape here, but with a single prop, it would be less probable to make any error during rebase inside that PR.

okay, let's proceed with this one and orientation then

src/components/tabs/useTabsHost.ts

src/components/tabs/TabsScreen.ios.tsx

src/fabric/tabs/TabsScreenIOSNativeComponent.ts

src/fabric/tabs/TabsHostAndroidNativeComponent.ts

common/cpp/react/renderer/components/rnscreens/RNSTabsHostShadowNode.h

common/cpp/react/renderer/components/rnscreens/RNSTabsHostShadowNode.cpp

t0maboro · 2026-03-04T15:24:39Z

One more question: what about bottom accessory: should it also have excludedPlatforms in spec file?

sure, we may consider it

Should the name be changed to TabsBottomAccessoryIOSNativeComponent or if this is already iOS-only component we don't need IOS part?

the only reason behind adding these suffixes was that codegen was iterating over files and generating duplicated symbols, when the name was RNSTabsScreen - that's why suffixes were necessary

kligarski · 2026-03-04T15:34:30Z

Should the name be changed to TabsBottomAccessoryIOSNativeComponent or if this is already iOS-only component we don't need IOS part?

the only reason behind adding these suffixes was that codegen was iterating over files and generating duplicated symbols, when the name was RNSTabsScreen - that's why suffixes were necessary

I understand but I wonder if maybe doing so even if it's not necessary by codegen would be better or not - advantage is that it would all be consistent across all files (e.g. in the future, if we have some files that have shared codegen spec, they wouldn't have any suffix but iOS-specific accessory would) but I guess that it is a bit redundant so I'm okay with both solutions.

t0maboro · 2026-03-04T15:43:12Z

I understand but I wonder if maybe doing so even if it's not necessary by codegen would be better or not - advantage is that it would all be consistent across all files (e.g. in the future, if we have some files that have shared codegen spec, they wouldn't have any suffix but iOS-specific accessory would) but I guess that it is a bit redundant so I'm okay with both solutions.

not a strong opinion, but I really don't like the fact that right now we're forced to have iOS in the name, e.g. react::RNSTabsScreenIOSIconType when this is applicable only for iOS, so I'd like to avoid that as much as possible, and treat TabsScreen and TabsHost as exceptions that we shouldn't follow by default

t0maboro · 2026-03-04T15:49:26Z

One more question: what about bottom accessory: should it also have excludedPlatforms in spec file?

c794ffb

kkafar

Great job.

Left few remarks & questions. Please answer them.

kkafar · 2026-03-09T15:21:46Z

apps/src/tests/component-integration-tests/orientation/orientation-stack-in-tabs.tsx

+          findTabScreenOptions(tabsConfig, 'Tab1')?.tabScreenProps.ios
+            ?.orientation ?? 'undefined'


This won't scale well. We need to refactor the BottomTabsContainer implementation.

I think this test won't be iOS only for a long time.

Not in scope of this PR obviously.

Could you provide some more details about that refactor?

https://github.com/software-mansion/react-native-screens-labs/issues/1040

I'll fill in the ticket

kkafar · 2026-03-09T15:25:51Z

apps/src/tests/component-integration-tests/orientation/orientation-stack-in-tabs.tsx

+                ios: {
+                  orientation: value === 'undefined' ? undefined : value,
+                },


I have an immediate question remark here though:

IIRC the version we settled on has been this one - orientation should be in general section.

kkafar · 2026-03-09T15:44:38Z

apps/src/tests/single-feature-tests/tabs/test-tabs-appearance-defined-by-selected-tab.tsx

 export default SCENARIO;

-const DEFAULT_APPEARANCE_ANDROID: TabsScreenAppearanceAndroid = {
+const DEFAULT_APPEARANCE_ANDROID: TabsScreenPropsAndroid.TabsScreenAppearance = {


kkafar · 2026-03-09T15:45:59Z

apps/src/tests/single-feature-tests/tabs/test-tabs-color-scheme.tsx

      <View style={styles.section}>
        <Text style={styles.heading}>TabsHost color scheme</Text>
-        <SettingsPicker<NonNullable<TabsHostProps['colorScheme']>>
+        <SettingsPicker<NonNullable<TabsHostPropsIOS.TabsHostColorScheme>>


ColorScheme also should not be iOS only, right @kligarski?

It will be shared after #3723 is merged but we decided to wait until this PR is merged before proceeding with #3723.

Prior to #3723, it is iOS-only.

kkafar · 2026-03-09T16:56:01Z

src/components/tabs/TabsHost.d.ts

+/**
+ * TS module resolution does not support this RN platform extension pattern out of the box.
+ * Without a base .tsx file, TS will throw a "Cannot find module" error.
+ *
+ * This file satisfies the TS compiler by providing the correct type signatures,
+ * whereas Metro will handle the proper runtime file resolution.
+ */


Thanks for explanation

kkafar · 2026-03-09T17:15:25Z

src/components/tabs/TabsHost.ios.types.ts

+  /**
+   * @summary Specifies the color scheme used by the container and any child containers.
+   *
+   * The following values are currently supported:
+   * - `inherit` - the interface style from parent,
+   * - `light` - the light interface style,
+   * - `dark` - the dark interface style.
+   *
+   * @default inherit
+   *
+   * @platform ios
+   */
+  colorScheme?: TabsHostColorScheme;


What do you guys think?

kkafar · 2026-03-09T17:15:50Z

src/components/tabs/TabsHost.ios.types.ts

+  /**
+   * @summary Specifies the color scheme used by the container and any child containers.
+   *
+   * The following values are currently supported:
+   * - `inherit` - the interface style from parent,
+   * - `light` - the light interface style,
+   * - `dark` - the dark interface style.
+   *
+   * @default inherit
+   *
+   * @platform ios
+   */
+  colorScheme?: TabsHostColorScheme;


Because we should be consistent for all such props

kkafar · 2026-03-09T17:28:06Z

src/components/tabs/TabsScreen.ios.types.ts

+export type TabsScreenBlurEffect =
+  | 'none'
+  | 'systemDefault'
+  | 'extraLight'
+  | 'light'
+  | 'dark'
+  | 'regular'
+  | 'prominent'
+  | 'systemUltraThinMaterial'
+  | 'systemThinMaterial'
+  | 'systemMaterial'
+  | 'systemThickMaterial'
+  | 'systemChromeMaterial'
+  | 'systemUltraThinMaterialLight'
+  | 'systemThinMaterialLight'
+  | 'systemMaterialLight'
+  | 'systemThickMaterialLight'
+  | 'systemChromeMaterialLight'
+  | 'systemUltraThinMaterialDark'
+  | 'systemThinMaterialDark'
+  | 'systemMaterialDark'
+  | 'systemThickMaterialDark'
+  | 'systemChromeMaterialDark';


Leaving a note here to remember to refactor this according to the discussion.

https://github.com/software-mansion/react-native-screens-labs/issues/1041

kkafar · 2026-03-09T17:31:06Z

src/components/tabs/useTabsHost.ts

+    } else {
+      componentNodeHandle.current = -1;
+    }
+  }, []);


This can be replaced with useRenderDebugInfo in general I think (another PR of course).

kkafar · 2026-03-09T17:37:18Z

src/components/tabs/index.ts

+// Namespace the Host platform-specific types
+export type * as TabsHostPropsAndroid from './TabsHost.android.types';
+export type * as TabsHostPropsIOS from './TabsHost.ios.types';
+
+// Namespace the Screen platform-types
+export type * as TabsScreenPropsAndroid from './TabsScreen.android.types';
+export type * as TabsScreenPropsIOS from './TabsScreen.ios.types';


Leaving a note here for future PRs - this wasn't settled. I don't like namespaceing here. I don't know any other big lib that does this. Let's see how this will look in the final PR.

kkafar

If we decide to leave orientation & colorScheme as platform specific right now, then let's proceed.

kkafar · 2026-03-09T21:02:38Z

Please update the PR description before merging. Right now you'll close only one of the issues. To close both, you need to repeat Closes xxx in two separate lines. I know...

t0maboro · 2026-03-09T21:03:53Z

If we decide to leave orientation & colorScheme as platform specific right now, then let's proceed.

@kkafar orientation moved up, because there's no PR related to it atm, colorScheme leaving it in its original PR, for all other remarks - I created tickets

t0maboro · 2026-03-09T21:04:35Z

Please update the PR description before merging. Right now you'll close only one of the issues. To close both, you need to repeat Closes xxx in two separate lines. I know...

updated

apps/src/tests/issue-tests/TestBottomTabsOrientation.tsx

## Description Omission from #3722 (comment) ## Changes - fixed icon - removed badge, as no badges are displayed ## Checklist - [ ] Included code example that can be used to test this change. - [ ] Updated / created local changelog entries in relevant test files. - [ ] For visual changes, included screenshots / GIFs / recordings documenting the change. - [ ] For API changes, updated relevant public types. - [ ] Ensured that CI passes

t0maboro added 6 commits March 4, 2026 11:11

JS layer + spec split

ed7699a

Fix android compilation issues

4b364a7

Fix ios compilation issues

05ce2bf

Update examples

4cce2a6

Move platform-specific types to separate files

c506ea1

Fix android after prop rename

2a46504

t0maboro requested a review from Copilot March 4, 2026 11:29

Copilot started reviewing on behalf of t0maboro March 4, 2026 11:30 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

src/components/tabs/TabsHost.ios.types.ts Outdated Show resolved Hide resolved

src/components/tabs/TabsHost.android.tsx Outdated Show resolved Hide resolved

src/fabric/tabs/TabsHostAndroidNativeComponent.ts Outdated Show resolved Hide resolved

Import as type

347e077

t0maboro requested review from kkafar, kligarski and kmichalikk March 4, 2026 12:02

t0maboro added 2 commits March 4, 2026 13:04

Remove layoutDirection from native spec for android

678d326

Drop controlNavigationStateFromJS from native spec on android

00ea926

t0maboro requested a review from Copilot March 4, 2026 12:20

Copilot started reviewing on behalf of t0maboro March 4, 2026 12:21 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

src/fabric/tabs/TabsScreenAndroidNativeComponent.ts Show resolved Hide resolved

t0maboro mentioned this pull request Mar 4, 2026

feat(Tabs, Android): handle colorScheme (dark mode) #3723

Merged

3 tasks

kligarski approved these changes Mar 4, 2026

View reviewed changes

t0maboro added 4 commits March 4, 2026 16:27

Drop prefixes

4f599bf

Move prop

50a1cb4

Move & sort props

016258f

Rename

b578626

t0maboro added 4 commits March 4, 2026 16:35

Suppress warnings

e2d9f31

move prop

5e4c232

Extract children from props

13a9fde

remove comment

8608af2

t0maboro added 4 commits March 4, 2026 16:38

Fix comment

a002828

Add comment

ac119f2

Add comments

b2caefd

Add comments

1b34b06

Exclude bottom accessory from android

c794ffb

Fix examples

f67f24c

kkafar reviewed Mar 9, 2026

View reviewed changes

kkafar approved these changes Mar 9, 2026

View reviewed changes

Move Orientation to base props

407f95b

t0maboro merged commit f2490d5 into main Mar 10, 2026
8 checks passed

t0maboro deleted the @t0maboro/tabs-split-components branch March 10, 2026 08:05

kkafar reviewed Mar 12, 2026

View reviewed changes

apps/src/tests/issue-tests/TestBottomTabsOrientation.tsx Show resolved Hide resolved

t0maboro mentioned this pull request Mar 12, 2026

fix(Examples): Fix TestBottomTabsOrientation #3757

Merged

5 tasks

		findTabScreenOptions(tabsConfig, 'Tab1')?.tabScreenProps.ios
		?.orientation ?? 'undefined'

Uh oh!

Conversation

t0maboro commented Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Changes

Before & after - visual documentation

Test plan

Checklist

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

kligarski left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

t0maboro commented Mar 4, 2026

Uh oh!

kligarski commented Mar 4, 2026

Uh oh!

t0maboro commented Mar 4, 2026

Uh oh!

t0maboro commented Mar 4, 2026

Uh oh!

kkafar left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

t0maboro commented Mar 4, 2026 •

edited

Loading

kkafar commented Mar 9, 2026 •

edited

Loading