| /expo/packages/expo-router/src/fork/ |
| H A D | NavigationContainer.tsx | 1 // We only need to fork on native to support any prefixes.
|
| /expo/react-native-lab/ |
| H A D | README.md | 7 The `react-native` directory is a Git submodule whose origin is `expo/react-native`. We keep it on … 17 …jects that use the unversioned (that is, latest) SDK, add them to `sdk-*`. We do this sparingly an… 19 …We need our React Native fork to stay perpetually close to upstream.** One way to think of our for… 23 …his branch is based on the latest stable release of React Native upstream. We cherry-pick in chang…
|
| /expo/docs/pages/feature-preview/ |
| H A D | index.mdx | 8 We decided to publish some of our new features as a preview to get feedback from you. It doesn't me…
|
| /expo/docs/pages/tutorial/ |
| H A D | follow-up.mdx | 13 We used React components and APIs. Having a solid understanding of React is essential to using Expo… 24 We used Flexbox to layout our components. Check out the following recommendations to learn more abo… 39 We had one screen in the tutorial app. Most apps have multiple screens. See [Routing](/routing/intr…
|
| H A D | create-your-first-app.mdx | 16 We'll need the following tools to get started: 27 We will use <A href="/more/glossary-of-terms/#create-expo-app">`create-expo-app`</A> to initialize … 53 description="We'll be using these assets throughout this tutorial." 99 We have created a new Expo project and are ready to develop our StickerSmash app.
|
| H A D | image-picker.mdx | 13 We want to build a feature that isn't possible with these core components and API: selecting an ima… 38 We can use the button with the primary theme we created in the previous chapter to pick an image fr… 39 We'll create a function to launch the device's image library to implement this functionality. 76 We can pass the object to specify different options when invoking the method. 159 We'll use this state variable to hold the URI of the selected image. 204 We'll need to pass the `selectedImage` prop to the component. 246 We added the functionality to pick an image from the device's media library.
|
| /expo/packages/expo-router/build/fork/ |
| H A D | NavigationContainer.js.map | 1 …";;AAAA,0DAA0D;AAC1D,qDAA+D;AAE/D,kBAAe,4BAAmB,CAAC","sourcesContent":["// We only need to fork on…
|
| /expo/packages/expo-modules-core/build/ |
| H A D | NativeModulesProxy.js.map | 1 …t":["import { ProxyNativeModule } from './NativeModulesProxy.types';\n\n// We default to an empty …
|
| /expo/fastlane/ |
| H A D | Matchfile | 7 # We default to appstore as we use match only for distribution certificates.
|
| /expo/packages/expo/ |
| H A D | CONTRIBUTING.md | 1 We've set up the Expo SDK to help us keep it reliable and clean and be confident in the changes we'… 37 We don't aim for 100% coverage. We want well-placed tests that keep the Expo SDK easy to work on wi… 51 …ell as the integration test suite. CI also runs the linter and TypeScript. We need to keep the CI … 55 We use ESLint with Prettier to detect some bugs and apply some of our style and formatting conventi… 63 We use TypeScript to add types to the Expo SDK, primarily for Expo developers using the SDK. TypeSc…
|
| /expo/ios/versioned-react-native/ABI49_0_0/ReactNative/React/CoreModules/ |
| H A D | ABI49_0_0RCTEventDispatcher.mm | 31 …// We need this lock to protect access to _events, _eventQueue and _eventsDispatchScheduled. It's … 34 // We have this id -> event mapping so we coalesce effectively. 89 …// We copy the string here because if it's a mutable string it may get released before we dispatch… 108 …// We copy the string here because if it's a mutable string it may get released before we dispatch… 163 // We have to release the lock before dispatching block with events,
|
| /expo/ios/versioned-react-native/ABI48_0_0/ReactNative/React/CoreModules/ |
| H A D | ABI48_0_0RCTEventDispatcher.mm | 31 …// We need this lock to protect access to _events, _eventQueue and _eventsDispatchScheduled. It's … 34 // We have this id -> event mapping so we coalesce effectively. 89 …// We copy the string here because if it's a mutable string it may get released before we dispatch… 108 …// We copy the string here because if it's a mutable string it may get released before we dispatch… 163 // We have to release the lock before dispatching block with events,
|
| /expo/apps/router-e2e/__e2e__/auth/app/ |
| H A D | _layout.tsx | 6 // We won't do any navigation or route protection in the root layout as this
|
| /expo/ios/versioned-react-native/ABI49_0_0/ReactNative/ReactCommon/ |
| H A D | ABI49_0_0React-rncore.podspec | 13 # We are using two different paths for react native because of the way how js_srcs_dir and output_d… 16 # We should rethink this approach in T148704916
|
| /expo/docs/pages/ |
| H A D | _error.tsx | 33 We took an educated guess and tried to direct you to the right page, but it seems that did not 48 We couldn't find the page you were looking for. Check the URL to make sure it's correct and 82 // We are confident now that we can render a not found error
|
| /expo/docs/pages/modules/ |
| H A D | native-module-tutorial.mdx | 11 …hat stores the user's preferred app theme - either dark, light, or system. We'll use [`UserDefault… 92 Now let's run the example project to make sure everything is working. We'll need to start the TypeS… 113 We should now see the text "Theme: system" in the center of the screen when we launch the example a… 121 To set the value, we can use `UserDefaults`'s `set(_:forKey:)` method. We'll make our `setTheme` fu… 143 …g under the key `"theme"`, and fall back to `"system"` if there isn't any. We can get the `SharedP… 145 … to get an `Editor` instance, and then use `putString()` to set the value. We'll make our `setThem… 195 We can now use the `Settings` API in our example app. 215 …because we're never fetching the new theme value and re-rendering the app. We'll fix this in the n… 219 We can ensure that developers using our API can react to changes in the theme value by emitting a c… 341 …API in its current form, because we can set the theme to any string value. We can improve the type… [all …]
|
| /expo/android/ |
| H A D | build.gradle | 17 // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP. 38 // We don't need linter on turtle. 68 // We don't want to fetch react-native from Maven Central as there are 137 // We don't need linter on turtle.
|
| /expo/packages/expo/.github/ |
| H A D | ISSUE_TEMPLATE.md | 1 We're looking to keep questions on our forums and bug reports on our main Expo repo -- please choos…
|
| /expo/packages/expo-file-system/ios/EXSessionTasks/ |
| H A D | EXSessionHandler.m | 34 // We need to run completionHandler explicite on the main thread because is's part of UIKit
|
| /expo/ios/versioned/sdk47/EXFileSystem/EXFileSystem/EXSessionTasks/ |
| H A D | ABI47_0_0EXSessionHandler.m | 34 // We need to run completionHandler explicite on the main thread because is's part of UIKit
|
| /expo/packages/eslint-config-universe/ |
| H A D | CONTRIBUTING.md | 1 We welcome contributions for bug fixes and are more conservative about changing the selected set of…
|
| /expo/ios/versioned/sdk48/EXFileSystem/EXFileSystem/EXSessionTasks/ |
| H A D | ABI48_0_0EXSessionHandler.m | 34 // We need to run completionHandler explicite on the main thread because is's part of UIKit
|
| /expo/ios/versioned/sdk49/EXFileSystem/EXFileSystem/EXSessionTasks/ |
| H A D | ABI49_0_0EXSessionHandler.m | 34 // We need to run completionHandler explicite on the main thread because is's part of UIKit
|
| /expo/docs/pages/eas-update/ |
| H A D | deployment-patterns.mdx | 10 We could push our code directly to production, which would be fast yet less safe since we never tes… 17 - (a) We can create builds for production use only. 18 …- (b) We can create builds for production use and separate builds for pre-production change testin… 20 - (a) We can test changes with TestFlight and Play Store Internal Track. 21 - (b) We can test changes with an internal distribution build. 22 …- (c) We can test changes with Expo Go or a [development build](/develop/development-builds/introd… 24 - (a) We can publish updates to a single branch. 25 - (b) We can create update branches that are environment-based, like "production" and "staging". 26 …- (c) We can create update branches that are version-based, like "version-1.0", which enables us t… 28 We can mix, match, and tweak the parts above to create a process that is the right balance of relea… [all …]
|
| /expo/ios/versioned/sdk47/EXFirebaseCore/EXFirebaseCore/ |
| H A D | ABI47_0_0EXFirebaseCoreAppDelegate.m | 14 // We provide no interface for customizing this app's Firebase configuration.
|