Janic Duplessis cf69c90c09 Fix flipper package | 4 years ago | |
---|---|---|
.github | 4 years ago | |
android | 4 years ago | |
example | 4 years ago | |
ios | 4 years ago | |
src | 4 years ago | |
.eslintignore | 4 years ago | |
.eslintrc.js | 4 years ago | |
.gitattributes | 4 years ago | |
.gitignore | 4 years ago | |
.prettierrc | 4 years ago | |
.watchmanconfig | 5 years ago | |
LICENSE | 5 years ago | |
README.md | 4 years ago | |
babel.config.js | 4 years ago | |
package.json | 4 years ago | |
react-native-safe-area-context.podspec | 4 years ago | |
tsconfig.json | 4 years ago | |
yarn.lock | 4 years ago |
A flexible way to handle safe area, also works on Android and Web!
Install the library using either Yarn:
yarn add react-native-safe-area-context
or npm:
npm install --save react-native-safe-area-context
You then need to link the native parts of the library for the platforms you are using. The easiest way to link the library is using the CLI tool by running this command from the root of your project:
react-native link react-native-safe-area-context
If you can’t or don’t want to use the CLI tool, you can also manually link the library using the instructions below (click on the arrow to show them):
Either follow the instructions in the React Native documentation to manually link the framework or link using Cocoapods by adding this to your Podfile
:
pod 'react-native-safe-area-context', :path => '../node_modules/react-native-safe-area-context'
Make the following changes:
android/settings.gradle
include ':react-native-safe-area-context'
project(':react-native-safe-area-context').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-safe-area-context/android')
android/app/build.gradle
dependencies {
...
implementation project(':react-native-safe-area-context')
}
android/app/src/main/.../MainApplication.java
On top, where imports are:
import com.th3rdwave.safeareacontext.SafeAreaContextPackage;
Add the SafeAreaContextPackage
class to your list of exported packages.
@Override
protected List<ReactPackage> getPackages() {
return Arrays.asList(
new MainReactPackage(),
...
new SafeAreaContextPackage()
);
}
Add SafeAreaProvider
in your app root component:
import { SafeAreaProvider } from 'react-native-safe-area-context';
function App() {
return <SafeAreaProvider>...</SafeAreaProvider>;
}
Usage with hooks api:
import { useSafeAreaInsets } from 'react-native-safe-area-context';
function HookComponent() {
const insets = useSafeAreaInsets();
return <View style={{ paddingTop: insets.top }} />;
}
Usage with consumer api:
import { SafeAreaInsetsContext } from 'react-native-safe-area-context';
class ClassComponent extends React.Component {
render() {
return (
<SafeAreaInsetsContext.Consumer>
{insets => <View style={{ paddingTop: insets.top }} />}
</SafeAreaInsetsContext.Consumer>
);
}
}
Usage with SafeAreaView
:
import { SafeAreaView } from 'react-native-safe-area-context';
function SomeComponent() {
return (
<SafeAreaView>
<View />
</SafeAreaView>
);
}
If you are doing server side rendering on the web you can use initialMetrics
to inject insets and frame value based on the device the user has, or simply pass zero values. Since insets measurement is async it will break rendering your page content otherwise.
To speed up the initial render, you can import initialWindowMetrics
from this package and set as the initialMetrics
prop on the provider as described in Web SSR. You cannot do this if your provider remounts, or you are using react-native-navigation
.
import {
SafeAreaProvider,
initialWindowMetrics
} from 'react-native-safe-area-context';
function App() {
return (
<SafeAreaProvider initialMetrics={initialWindowMetrics}>
...
</SafeAreaProvider>
);
}