Skip to content

Commit b326b3e

Browse files
committed
Use admonitions syntax for notes
1 parent 4d83804 commit b326b3e

File tree

4 files changed

+20
-4
lines changed

4 files changed

+20
-4
lines changed

versioned_docs/version-7.x/header-buttons.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,11 @@ function MyStack() {
6969

7070
When we define our button this way, the `this` variable in `options` is _not_ the `HomeScreen` instance, so you can't call `setState` or any instance methods on it. This is pretty important because it's common to want the buttons in your header to interact with the screen that the header belongs to. So, we will look how to do this next.
7171

72-
> 💡 Please note that a community-developed library for rendering buttons in the header with the correct styling is available: [react-navigation-header-buttons](https://github.com/vonovak/react-navigation-header-buttons).
72+
:::tip
73+
74+
Note that a community-developed library for rendering buttons in the header with the correct styling is available: [react-navigation-header-buttons](https://github.com/vonovak/react-navigation-header-buttons).
75+
76+
:::
7377

7478
## Header interaction with its screen component
7579

versioned_docs/version-7.x/hello-react-navigation.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,11 @@ The libraries we've installed so far are the building blocks and shared foundati
2121
npm install @react-navigation/native-stack@next
2222
```
2323

24-
> 💡 `@react-navigation/native-stack` depends on `react-native-screens` and the other libraries that we installed in [Getting started](getting-started.md). If you haven't installed those yet, head over to that page and follow the installation instructions.
24+
:::info
25+
26+
`@react-navigation/native-stack` depends on `react-native-screens` and the other libraries that we installed in [Getting started](getting-started.md). If you haven't installed those yet, head over to that page and follow the installation instructions.
27+
28+
:::
2529

2630
### Creating a native stack navigator
2731

versioned_docs/version-7.x/native-stack-navigator.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,11 @@ npm install @react-navigation/native-stack@next
2020

2121
## API Definition
2222

23-
> 💡 If you encounter any bugs while using `createNativeStackNavigator`, please open issues on [`react-native-screens`](https://github.com/software-mansion/react-native-screens) rather than the `react-navigation` repository!
23+
:::info
24+
25+
If you encounter any bugs while using `createNativeStackNavigator`, please open issues on [`react-native-screens`](https://github.com/software-mansion/react-native-screens) rather than the `react-navigation` repository!
26+
27+
:::
2428

2529
To use this navigator, import it from `@react-navigation/native-stack`:
2630

versioned_docs/version-7.x/navigation-object.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,11 @@ The `navigation` object contains various convenience functions that dispatch nav
1818

1919
The `navigation` object can be accessed inside any screen component with the [`useNavigation`](use-navigation.md) hook. It's also passed as a prop only to screens components defined with the dynamic API.
2020

21-
> `setParams`/`setOptions` etc. should only be called in event listeners or `useEffect`/`useLayoutEffect`/`componentDidMount`/`componentDidUpdate` etc. Not during render or in constructor.
21+
:::warning
22+
23+
`setParams`/`setOptions` etc. should only be called in event listeners or `useEffect`/`useLayoutEffect`/`componentDidMount`/`componentDidUpdate` etc. Not during render or in constructor.
24+
25+
:::
2226

2327
### Navigator-dependent functions
2428

0 commit comments

Comments
 (0)