Skip to content

Commit 3e8abe4

Browse files
authored
fix(issue #1038) Dead link Configuring the header bar page (#1074)
1 parent 27980eb commit 3e8abe4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

versioned_docs/version-6.x/headers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ function StackScreen() {
166166
<Stack.Screen
167167
name="Home"
168168
component={HomeScreen}
169-
options={{ headerTitle: props => <LogoTitle {...props} /> }}
169+
options={{ headerTitle: (props) => <LogoTitle {...props} /> }}
170170
/>
171171
</Stack.Navigator>
172172
);
@@ -177,10 +177,10 @@ function StackScreen() {
177177
178178
## Additional configuration
179179

180-
You can read the full list of available `options` for screens inside of a native stack navigator in the [`createNativeStackNavigator` reference](native-stack-navigator#options).
180+
You can read the full list of available `options` for screens inside of a native stack navigator in the [`createNativeStackNavigator` reference](native-stack-navigator.md#options).
181181

182182
## Summary
183183

184-
- You can customize the header inside of the `options` prop of your screen components. Read the full list of options [in the API reference](native-stack-navigator#options).
184+
- You can customize the header inside of the `options` prop of your screen components. Read the full list of options [in the API reference](native-stack-navigator.md#options).
185185
- The `options` prop can be an object or a function. When it is a function, it is provided with an object with the `navigation` and `route` prop.
186186
- You can also specify shared `screenOptions` in the stack navigator configuration when you initialize it. The prop takes precedence over that configuration.

0 commit comments

Comments
 (0)