chore: Remove other mentions of legacy Example app (#3642)

## Description

This PR removes some leftover mentions of legacy Example app.

## Changes

Removed text instance of Example/ScreensExample. Removed
NEW_ARCH_ENABLED env from podfile (it's default now, and was put for
consistency with now removed Example)

## Before & after - visual documentation

no visual changes

## Checklist

- [ ] Ensured that CI passes

Author: kmichalikk

FabricExample/e2e/examplesTests/events.e2e.ts

@@ -12,7 +12,7 @@ const pressBack = async () => {
 
 const awaitClassicalEventBehavior = async () => {
   if (device.getPlatform() === 'ios') {
-    // The order of events in this test differs from the Paper version of the same test.
+    // The order of events in this test differs from Paper.
     // Please see https://github.com/software-mansion/react-native-screens/pull/2785 for details.
     await expect(
       element(by.text('9. Chats | transitionStart | closing')),

FabricExample/ios/Podfile

@@ -11,9 +11,6 @@ require_relative '../../scripts/ios/rns_set_swift_compilation_flags'
 platform :ios, min_ios_version_supported
 prepare_react_native_project!
 
-# From 0.76 new arch is enabled by default, we just want to have it explicitly set and for consistency with Example app
-ENV['RCT_NEW_ARCH_ENABLED'] = '1'
-
 # Disable precompiled binaries for RN core
 ENV['RCT_USE_PREBUILT_RNCORE'] = '0'
 

guides/CONTRIBUTING.md

@@ -41,7 +41,6 @@ We inform you that unrespectful issues will be closed.
 - `common` – C++ code related to components - shadow nodes and state
 - `cpp` – C++ code for turbo modules
 - `apps` – apps implementations shared by wrappers
-- `Example` – paper version of React Native mobile example app from apps
 - `FabricExample` – fabric version of React Native mobile example app from apps
 - `gesture-handler` – interop between react-native-screens and react-native-gesture-handler
 - `guides` – guides for developers
@@ -72,13 +71,11 @@ Submitting Pull Requests that resolve issues is a great way to contribute to Scr
 > [!tip]
 > For commits and pull request names we follow a [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification.
 
-We have two types of sources: pure examples (apps/Example for source code) and examples, dedicated for tests from issues / pull requests (apps/src/tests for source code). The first work as a showcase of the library, the latter contains specific test cases that corresponds to GitHub issues. For example, `Test1864.tsx` corresponds to issue [#1864](https://github.com/software-mansion/react-native-screens/issues/1864). Our developer flow usually consists of creating new `Test*.tsx` file with code example that we try to fix or add. For new features we try to prepare showcases in Example app. The `apps/App` file is where you set the source code for the application to use by either leaving `<Example>` as is or replacing it with `<Test.Test*>`.
-There are two separate applications: Example and FabricExample in root which are used as wrappers for running the examples depending on the architecture needed.
+We have two types of sources: pure examples (apps/Example for source code) and examples, dedicated for tests from issues / pull requests (apps/src/tests for source code). The former work as a showcase of the library, the latter contain isolated props' behavior, selected interactions between props, and specific test cases that corresponds to GitHub issues. For example, `Test1864.tsx` corresponds to issue [#1864](https://github.com/software-mansion/react-native-screens/issues/1864). Our developer flow usually consists of creating new `Test*.tsx` file with code example that we try to fix or add. For new features we try to prepare dedicated showcases. The `apps/App` file is where you set the source code for the application to use by either leaving `<Example>` as is or replacing it with `<Test.Test*>`.
 
 - `apps/Example` &ndash; source code with showcase app
 - `apps/src/tests` &ndash; source code with test examples app
 - `apps/App` &ndash; source code management
-- `Example/src` &ndash; wrapper with paper architecture for showcase and test examples app
 - `FabricExample/src` &ndash; wrapper with fabric architecture for showcase and test examples app
 - `TVOSExample/src` &ndash; source code with example app for TVOS
 - `src` &ndash; contains JS core code of the library
@@ -91,11 +88,11 @@ To begin with, let install all dependencies:
 
 1. `yarn`
 2. `yarn submodules`
-4. `cd Example` or `cd FabricExample` (depending on architecture you want to work on)
+4. `cd FabricExample`
 5. `yarn`
 6. `yarn start` &ndash; make sure to start metro bundler before building the app in Android Studio
 
-and open `react-native-screens/Example/android` with Android Studio.
+and open `react-native-screens/FabricExample/android` with Android Studio.
 
 ![Android Studio](android_studio.png)
 
@@ -107,17 +104,17 @@ To begin with, let install all dependencies:
 
 1. `yarn`
 2. `yarn submodules`
-3. `cd Example` or `cd FabricExample`
+3. `cd FabricExample`
 4. `yarn`
 5. `rbenv exec bundle install`
 6. `(cd ios && rbenv exec bundle exec pod install && cd ../)`
 7. `yarn start` &ndash; make sure to start metro bundler before building the app in XCode.
 
-and open `react-native-screens/Example/ios/ScreensExample.xcworkspace` with XCode.
+and open `react-native-screens/FabricExample/ios/FabricExample.xcworkspace` with XCode.
 
 ![XCode](xcode.png)
 
-To find the native source code of `react-native-screens` navigate to `Pods > Development Pods >  RNScreens > ScreensExample > node_modules > react-native-screens > ios` or `Pods > Development Pods > RNScreens > .. > ScreensExample > node_modules > react-native-screens > ios`. Making sure metro builder is run, you can now build React Native app or debug native code.
+To find the native source code of `react-native-screens` navigate to `Pods > Development Pods >  RNScreens > FabricExample > node_modules > react-native-screens > ios` or `Pods > Development Pods > RNScreens > .. > FabricExample > node_modules > react-native-screens > ios`. Making sure metro builder is run, you can now build React Native app or debug native code.
 
 ### Fabric
 

guides/GUIDE_FOR_LIBRARY_AUTHORS.md

@@ -854,16 +854,12 @@ In order for your native view on iOS to be notified when its parent navigation c
 }
 ```
 
-You can check our example app for a fully functional demo see [RNSSampleLifecycleAwareView.m](https://github.com/software-mansion/react-native-screens/blob/main/Example/ios/ScreensExample/RNSSampleLifecycleAwareView.m) for more details.
-
 ## Navigation lifecycle on Android
 
 On Android, you can use [LifecycleObserver](https://developer.android.com/reference/android/arch/lifecycle/LifecycleObserver) interface which is a part of Android compat library to make your view handle lifecycle events.
-Check [LifecycleAwareView.java](https://github.com/software-mansion/react-native-screens/blob/main/Example/android/app/src/main/java/com/swmansion/rnscreens/example/LifecycleAwareView.java) from our example app for more details on that.
 
 In addition to that, you will need to register for receiving these updates. This can be done using [`LifecycleHelper.register`](https://github.com/software-mansion/react-native-screens/blob/main/android/src/main/java/com/swmansion/rnscreens/LifecycleHelper.java#L50).
 Remember to call [`LifecycleHelper.unregister`](https://github.com/software-mansion/react-native-screens/blob/main/android/src/main/java/com/swmansion/rnscreens/LifecycleHelper.java#L59) before the view is dropped.
-Please refer to [SampleLifecycleAwareViewManager.java](https://github.com/software-mansion/react-native-screens/blob/main/Example/android/app/src/main/java/com/swmansion/rnscreens/example/SampleLifecycleAwareViewManager.java) from our example app to see what are the best ways of using the above methods.
 
 ## Android hardware back button
 

jest.config.js

@@ -1,4 +1,4 @@
 module.exports = {
   preset: 'react-native',
-  modulePathIgnorePatterns: [],
+  modulePathIgnorePatterns: ['FabricExample'],
 };

package.json

@@ -7,7 +7,7 @@
     "check-types": "tsc --noEmit",
     "start": "react-native start",
     "test:unit": "jest --passWithNoTests",
-    "format-js": "prettier --write --list-different './src/**/*.{js,ts,tsx}'",
+    "format-js": "prettier --write --list-different './{src,FabricExample}/**/*.{js,ts,tsx}'",
     "format-android": "node ./scripts/format-android.js",
     "format-ios-swift": "sh scripts/swift-format-helper.sh format",
     "format-ios-cpp": "find ios/ -iname \"*.h\" -o -iname \"*.m\" -o -iname \"*.cpp\" -o -iname \"*.mm\" | xargs clang-format -i",
@@ -124,7 +124,7 @@
     "typescript": "^5.8.3"
   },
   "lint-staged": {
-    "src/**/*.{js,ts,tsx}": "yarn format-js",
+    "{src,FabricExample}/**/*.{js,ts,tsx}": "yarn format-js",
     "FabricExample/ios/**/*.swift": "yarn format-ios-swift",
     "src/**/*.{js,ts,tsx}": "yarn lint-js",
     "common/**/*.{h,cpp}": "yarn format-common",

scripts/e2e/detox-utils.cjs

@@ -48,7 +48,7 @@ const testButlerApkPath = isRunningCI
  * Example: `RNS_IOS_VERSION="iOS 18.6" RNS_APPLE_SIM_NAME="iPhone 17 Pro" yarn test-e2e-ios` will fail
  * as iPhone 17 Pro was released with iOS 26
  *
- * @param {string} applicationName name (FabricExample / ScreensExample)
+ * @param {string} applicationName name (FabricExample)
  * @returns {Detox.DetoxConfig}
  */
 function commonDetoxConfigFactory(applicationName) {

tsconfig.build.json

@@ -1,4 +1,4 @@
 {
   "extends": "./tsconfig",
-  "exclude": ["TVOSExample"]
+  "exclude": ["FabricExample", "TVOSExample"]
 }