Skip to content

docs: Fixed typo in v7 #1364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Aug 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions versioned_docs/version-7.x/handling-safe-area.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,15 +65,15 @@ function Demo() {

// codeblock-focus-start
const MyTabs = createBottomTabNavigator({
initialRouteName: 'Analitics',
initialRouteName: 'Analytics',
// highlight-start
tabBar: () => null,
screenOptions: {
headerShown: false,
},
// highlight-end
screens: {
Analitics: Demo,
Analytics: Demo,
Profile: Demo,
},
});
Expand Down Expand Up @@ -133,11 +133,11 @@ export default function App() {
<Stack.Screen name="Home">
{() => (
<Tab.Navigator
initialRouteName="Analitics"
initialRouteName="Analytics"
tabBar={() => null}
screenOptions={{ headerShown: false }}
>
<Tab.Screen name="Analitics" component={Demo} />
<Tab.Screen name="Analytics" component={Demo} />
<Tab.Screen name="Profile" component={Demo} />
</Tab.Navigator>
)}
Expand Down Expand Up @@ -195,13 +195,13 @@ function Demo() {
// codeblock-focus-end

const MyTabs = createBottomTabNavigator({
initialRouteName: 'Analitics',
initialRouteName: 'Analytics',
tabBar: () => null,
screenOptions: {
headerShown: false,
},
screens: {
Analitics: Demo,
Analytics: Demo,
Profile: Demo,
},
});
Expand Down Expand Up @@ -285,11 +285,11 @@ export default function App() {
<Stack.Screen name="Home">
{() => (
<Tab.Navigator
initialRouteName="Analitics"
initialRouteName="Analytics"
tabBar={() => null}
screenOptions={{ headerShown: false }}
>
<Tab.Screen name="Analitics" component={Demo} />
<Tab.Screen name="Analytics" component={Demo} />
<Tab.Screen name="Profile" component={Demo} />
</Tab.Navigator>
)}
Expand Down Expand Up @@ -363,13 +363,13 @@ function Demo() {
// codeblock-focus-end

const MyTabs = createBottomTabNavigator({
initialRouteName: 'Analitics',
initialRouteName: 'Analytics',
tabBar: () => null,
screenOptions: {
headerShown: false,
},
screens: {
Analitics: Demo,
Analytics: Demo,
Profile: Demo,
},
});
Expand Down Expand Up @@ -448,11 +448,11 @@ export default function App() {
<Stack.Screen name="Home">
{() => (
<Tab.Navigator
initialRouteName="Analitics"
initialRouteName="Analytics"
tabBar={() => null}
screenOptions={{ headerShown: false }}
>
<Tab.Screen name="Analitics" component={Demo} />
<Tab.Screen name="Analytics" component={Demo} />
<Tab.Screen name="Profile" component={Demo} />
</Tab.Navigator>
)}
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-7.x/limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Limitations
sidebar_label: Limitations
---

As a potential user of the library, it's important to know what you can and cannot do with it. Armed with this knowledge, you may choose to adopt a different library such as [`react-native=navigation`](https://github.com/wix/react-native-navigation) instead. We discuss the high level design decisions in the [pitch & anti-pitch](pitch.md) section, and here we will cover some of the use cases that are either not supported or are so difficult to do that they may as well be impossible. If any of the following limitations are dealbreakers for your app, React Navigation might not be for you.
As a potential user of the library, it's important to know what you can and cannot do with it. Armed with this knowledge, you may choose to adopt a different library such as [`react-native-navigation`](https://github.com/wix/react-native-navigation) instead. We discuss the high level design decisions in the [pitch & anti-pitch](pitch.md) section, and here we will cover some of the use cases that are either not supported or are so difficult to do that they may as well be impossible. If any of the following limitations are dealbreakers for your app, React Navigation might not be for you.

## Limited right-to-left (RTL) layout support

Expand Down
Loading