Skip to content

Commit c6e3e8e

Browse files
committed
Upgrade docusaurus
1 parent 1abf318 commit c6e3e8e

184 files changed

Lines changed: 3494 additions & 2433 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.prettierrc.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,17 @@
11
{
2+
"overrides": [
3+
{
4+
"files": [
5+
"src/pages/**/*.md",
6+
"blog/*.md",
7+
"docs/**/*.md",
8+
"versioned_docs/**/*.md"
9+
],
10+
"options": {
11+
"parser": "mdx"
12+
}
13+
}
14+
],
215
"singleQuote": true,
316
"tabWidth": 2,
417
"trailingComma": "es5",

blog/2018-02-06-react-navigation-1.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ tags: [release, announcement]
66

77
As of today, React Navigation version 1.0 has been released! To see a list of recent improvements leading up to the release, refer to the “[Renewed Path to React Navigation V1.0](https://github.com/react-navigation/react-navigation/issues/2585)” issue. Thank you to everybody who has filed high-quality bug reports, submitted pull requests, and helped out fellow developers while we were in beta!
88

9-
<!--truncate-->
9+
{/* truncate */}
1010

1111
This release isn’t meant to be interpreted as a signal that React Navigation is “finished" &mdash; work is already underway on a number of significant changes to the API that aim to make React Navigation easier to use and more powerful. These changes will be run through our [new RFC process](https://github.com/react-navigation/rfcs). For example, the [Navigator View API RFC](https://github.com/react-navigation/rfcs/blob/master/text/0002-navigator-view-api.md) outlines a plan to decouple views from the router in order to make it easier for other navigation APIs, such as [react-native-router-flux](https://github.com/aksonov/react-native-router-flux) and [react-router-native](https://github.com/ReactTraining/react-router/tree/master/packages/react-router-native), to build on top of the same navigation views. We’re also very excited about a plan (no RFC is open yet, but keep an eye out for it) to use [react-native-gesture-handler](https://github.com/software-mansion/react-native-gesture-handler) to run navigation gestures (sliding a drawer open, or swiping back on a stack, for example) on the UI thread using the Animated native driver.
1212

blog/2018-04-06-react-navigation-2.0-rc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ tags: [release, announcement]
66

77
Exactly two months after the release of React Navigation 1.0, we are close to another major version release. We’d like to invite developers that use the library to give the release candidate a try in your app and let us know if you encounter any issues.
88

9-
<!--truncate-->
9+
{/* truncate */}
1010

1111
```bash
1212
yarn add react-navigation@^2.0.0-rc.1

blog/2018-05-07-react-navigation-2.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ tags: [release, announcement]
66

77
The documentation is now live at [reactnavigation.org](https://reactnavigation.org), and v1 lives [here](/docs/1.x/getting-started).
88

9-
<!--truncate-->
9+
{/* truncate */}
1010

1111
## Significant breaking changes
1212

blog/2018-11-01-react-navigation-3.0-rc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ We are excited to announce the release candidate of version 3.0 today!
88

99
This is the first release where React Navigation depends on a native module outside of React Native core: it now depends on react-native-gesture-handler. This library provides an excellent set of primitives for leveraging the operating systems’ native gesture APIs and has enabled us to fix a variety of issues with stack and drawer navigators. React Navigation also depends on react-native-screens, but you don’t need to install the native module if you prefer not to use it (we have a blog post coming soon that will explain what react-native-screens is and why you may want to use it, or you can watch [this talk](https://www.youtube.com/watch?v=Z0Jl1KCWiag) by the author of the library).
1010

11-
<!--truncate-->
11+
{/* truncate */}
1212

1313
We didn’t get around to every feature that we wanted to land for this release, but we also didn’t want to hold it up further because we expect that you will want to start using it right away - the release includes performance improvements, bugfixes, ergonomics improvements, some handy new features, and a re-organizing of the internals to improve support for web as a target of React Navigation.
1414

blog/2018-11-17-react-navigation-3.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ The documentation is now live at [reactnavigation.org](https://reactnavigation.o
88

99
This is the first release where React Navigation depends on a native module outside of React Native core: it now depends on react-native-gesture-handler. This library provides an excellent set of primitives for leveraging the operating systems’ native gesture APIs and has enabled us to fix a variety of issues with stack and drawer navigators. React Navigation also depends on react-native-screens, but you don’t need to install the native module if you prefer not to use it (we have a blog post coming soon that will explain what react-native-screens is and why you may want to use it, or you can watch [this talk](https://www.youtube.com/watch?v=Z0Jl1KCWiag) by the author of the library).
1010

11-
<!--truncate-->
11+
{/* truncate */}
1212

1313
We didn’t get around to every feature that we wanted to land for this release, but we also didn’t want to hold it up further because we expect that you will want to start using it right away - the release includes performance improvements, bugfixes, ergonomics improvements, some handy new features, and a re-organizing of the internals to improve support for web as a target of React Navigation.
1414

blog/2019-09-16-react-navigation-4.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ The documentation is now live at [reactnavigation.org](https://reactnavigation.o
88

99
In this release, we have removed the navigators from the react-navigation package. The navigators have lived in separate packages for quite a while and you could already use those packages manually, but we still bundled them in the react-navigation package. This made it difficult for us to release significant updates to navigators, because we had to then do a major version release of react-navigation too. By separating the navigator packages there is more freedom to update and improve navigators without any impact on folks that don't use them.
1010

11-
<!--truncate-->
11+
{/* truncate */}
1212

1313
For example, you will find when you install the latest versions of the drawer and tab navigators that the animations are more performant because they use react-native-reanimated to smoothly animate gestures. These have been available in react-navigation-drawer and react-navigation-tabs for several months now but we delayed updating them in react-navigation itself because we did not want to force every user to update.
1414

blog/2019-10-17-react-navigation-native.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ tags: [announcement]
66

77
React Navigation steps firmly into the next level and we’re very excited to announce to you something great happening in React Navigation codebase.
88

9-
<!--truncate-->
9+
{/* truncate */}
1010

1111
## Make it custom
1212

@@ -32,8 +32,16 @@ After years of growing development, we need to admit that we’re not always abl
3232

3333
Thanks to the great work of Krzysztof Magiera for [React Native Screens](https://github.com/kmagiera/react-native-screens) library now we can use truly native components instead of JS replicas.
3434

35-
<img src="/assets/blog/5.x/android-native-stack.gif" height="530" alt="Native Stack on Android" />
36-
<img src="/assets/blog/5.x/ios-native-stack.gif" height="530" alt="Native Stack on iOS" />
35+
<img
36+
src="/assets/blog/5.x/android-native-stack.gif"
37+
height="530"
38+
alt="Native Stack on Android"
39+
/>
40+
<img
41+
src="/assets/blog/5.x/ios-native-stack.gif"
42+
height="530"
43+
alt="Native Stack on iOS"
44+
/>
3745

3846
We believe you will find it useful in your projects and strongly encourage you to get acquainted with our [documentation](https://github.com/kmagiera/react-native-screens/native-stack). Things that I’m the most excited about are iOS header animations!
3947

blog/2019-11-04-using-react-navigation-5-with-ui-kitten.md

Lines changed: 30 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ tags: [tutorial, ui-kitten]
77
This is a guest post by the [UI Kitten](http://akveo.github.io/react-native-ui-kitten) team. If you like this guide, checkout UI Kitten for more!
88
In this blog post, we'll show a step-by-step guide on using React Navigation 5 with UI Kitten.
99

10-
<!--truncate-->
10+
{/* truncate */}
1111

1212
## Introduction
1313

@@ -17,7 +17,11 @@ The new React Navigation comes with several significant improvements such as [im
1717

1818
The UI Kitten team started actively using React Navigation alpha and we're proud to announce the full compatibility to the new React Navigation API. In this guide, we won't consider how to implement all of the boilerplate stuff like auth screens. Instead, we will learn how to navigate between screens using Drawer, Bottom Tabs, Top Tabs, and Stack navigators to build a TODO-App. Furthermore, we'll demonstrate using React Navigation with UI Kitten components.
1919

20-
<img src="/assets/blog/using-react-navigation-5-with-ui-kitten/overview.gif" height="480" alt="React Navigation with UI Kitten Overview" />
20+
<img
21+
src="/assets/blog/using-react-navigation-5-with-ui-kitten/overview.gif"
22+
height="480"
23+
alt="React Navigation with UI Kitten Overview"
24+
/>
2125

2226
## Overview
2327

@@ -90,7 +94,11 @@ export const AppNavigator = (): React.ReactElement => (
9094
);
9195
```
9296

93-
<img src="/assets/blog/using-react-navigation-5-with-ui-kitten/stack-navigator.gif" height="420" alt="UI Kitten with Stack Navigator" />
97+
<img
98+
src="/assets/blog/using-react-navigation-5-with-ui-kitten/stack-navigator.gif"
99+
height="420"
100+
alt="UI Kitten with Stack Navigator"
101+
/>
94102

95103
### Step 2. Top tabs
96104

@@ -182,7 +190,11 @@ export const AppNavigator = (props): React.ReactElement => (
182190
);
183191
```
184192

185-
<img src="/assets/blog/using-react-navigation-5-with-ui-kitten/material-top-tab-navigator.gif" height="480" alt="UI Kitten with Material Top Tabs" />
193+
<img
194+
src="/assets/blog/using-react-navigation-5-with-ui-kitten/material-top-tab-navigator.gif"
195+
height="480"
196+
alt="UI Kitten with Material Top Tabs"
197+
/>
186198

187199
### Step 3. Bottom tabs
188200

@@ -296,7 +308,11 @@ export const AppNavigator = (props): React.ReactElement => (
296308
);
297309
```
298310

299-
<img src="/assets/blog/using-react-navigation-5-with-ui-kitten/bottom-tab-navigator.gif" height="480" alt="UI Kitten with Bottom Tabs" />
311+
<img
312+
src="/assets/blog/using-react-navigation-5-with-ui-kitten/bottom-tab-navigator.gif"
313+
height="480"
314+
alt="UI Kitten with Bottom Tabs"
315+
/>
300316

301317
### Step 4. Drawer menu
302318

@@ -432,7 +448,11 @@ export const TodoTabBar = (props): SafeAreaLayoutElement => {
432448
};
433449
```
434450

435-
<img src="/assets/blog/using-react-navigation-5-with-ui-kitten/drawer-navigator.gif" height="420" alt="UI Kitten with Drawer" />
451+
<img
452+
src="/assets/blog/using-react-navigation-5-with-ui-kitten/drawer-navigator.gif"
453+
height="420"
454+
alt="UI Kitten with Drawer"
455+
/>
436456

437457
### TypeScript
438458

@@ -469,7 +489,10 @@ export interface ResetPasswordScreenProps {
469489

470490
Now you can modify props of Auth screens props by adding types to make your autocomplete and IntelliSense work. For more complex examples, consider reading [type-checking](/docs/typescript) doc or reviewing [complete demo application sources](https://github.com/artyorsh/react-navigation-ex-demo/tree/complete-exmaples).
471491

472-
<img src="/assets/blog/using-react-navigation-5-with-ui-kitten/typescript.gif" alt="UI Kitten & TypeScript" />
492+
<img
493+
src="/assets/blog/using-react-navigation-5-with-ui-kitten/typescript.gif"
494+
alt="UI Kitten & TypeScript"
495+
/>
473496

474497
### Useful links
475498

blog/2020-01-29-using-react-navigation-5-with-react-native-paper.md

Lines changed: 43 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ This is a guest post by the [React Native Paper](https://reactnativepaper.com/)
88

99
In this blog post, we'll show you how to build a Twitter clone app using React Navigation v5 and Paper.
1010

11-
<!--truncate-->
11+
{/* truncate */}
1212

1313
## Introduction
1414

@@ -24,7 +24,11 @@ In this guide, we would like to show you how to integrate React Navigation with
2424

2525
In the following gif, you can see what is the final version of the app gonna looks like:
2626

27-
<img src="/assets/blog/using-react-navigation-5-with-paper/final-app.gif" height="480" alt="Final Result" />
27+
<img
28+
src="/assets/blog/using-react-navigation-5-with-paper/final-app.gif"
29+
height="480"
30+
alt="Final Result"
31+
/>
2832

2933
## Overview of the App
3034

@@ -139,7 +143,11 @@ export const RootNavigator = () => {
139143

140144
That's what we see on a screen:
141145

142-
<img src="/assets/blog/using-react-navigation-5-with-paper/simple-drawer.gif" height="480" alt="Simple Drawer" />
146+
<img
147+
src="/assets/blog/using-react-navigation-5-with-paper/simple-drawer.gif"
148+
height="480"
149+
alt="Simple Drawer"
150+
/>
143151

144152
We can open a drawer with a swipe gesture, it looks very smooth. However, the UI doesn't look very impressive so let's add more content to the drawer to make it look just like in the final version.
145153

@@ -302,7 +310,11 @@ const styles = StyleSheet.create({
302310

303311
The final version of a drawer looks like this:
304312

305-
<img src="/assets/blog/using-react-navigation-5-with-paper/final-drawer.gif" height="480" alt="Drawer with components from React Native Paper" />
313+
<img
314+
src="/assets/blog/using-react-navigation-5-with-paper/final-drawer.gif"
315+
height="480"
316+
alt="Drawer with components from React Native Paper"
317+
/>
306318

307319
## Stack Navigator + Paper's Appbar
308320

@@ -430,8 +442,10 @@ The Function that we pass to `header` prop has access to 3 properties:
430442

431443
Thanks to the **scene** property we can access the title of topmost screen on the stack and display it in the header.
432444
**Previous** property tells us if there are any other screens lower on the Stack.
445+
433446
<br />
434-
Finally, **navigation** property allows navigating to different screens e.g. opening a Drawer.
447+
Finally, **navigation** property allows navigating to different screens e.g.
448+
opening a Drawer.
435449

436450
The thing that we haven't covered yet and it is very important is how to actually navigate between Stack Navigator screens.
437451
In case of Tab or Drawer Navigator, we get it out of the box. We can swipe to open/close the Drawer or press a tab to change the scene. In Stack, we have to implement it by ourselves.
@@ -456,7 +470,11 @@ We have covered only the basics of navigating between screens. If you want to le
456470

457471
Now, let's see what does the app looks like with Stack Navigator and Paper's Appbar.
458472

459-
<img src="/assets/blog/using-react-navigation-5-with-paper/stack.gif" height="480" alt="Stack Navigator with React Native Paper's Appbar" />
473+
<img
474+
src="/assets/blog/using-react-navigation-5-with-paper/stack.gif"
475+
height="480"
476+
alt="Stack Navigator with React Native Paper's Appbar"
477+
/>
460478

461479
We still miss the last piece of our navigation flow - **Tab Navigator**. Let's move to the next section where we will take care of it.
462480

@@ -526,7 +544,11 @@ export const BottomTabs = () => {
526544
When we check the screen of the phone now, we will see a nice looking, material bottom navigation. What's more, Stack Navigator integrates nicely with Tab.Navigator and we can still navigate to the tweet `Details` screen.
527545

528546
<br />
529-
<img src="/assets/blog/using-react-navigation-5-with-paper/bottom-navigation.gif" height="480" alt="Stack Navigator with Material Bottom Tabs" />
547+
<img
548+
src="/assets/blog/using-react-navigation-5-with-paper/bottom-navigation.gif"
549+
height="480"
550+
alt="Stack Navigator with Material Bottom Tabs"
551+
/>
530552

531553
## FAB and Portal
532554

@@ -745,7 +767,11 @@ export const BottomTabs = (props) => {
745767
};
746768
```
747769
748-
<img src="/assets/blog/using-react-navigation-5-with-paper/fab.gif" height="480" alt="React Native Paper's FAB with Bottom Tabs" />
770+
<img
771+
src="/assets/blog/using-react-navigation-5-with-paper/fab.gif"
772+
height="480"
773+
alt="React Native Paper's FAB with Bottom Tabs"
774+
/>
749775
750776
As you can see on the gif, the FAB button works in the same way as in a Twitter app.
751777
What's more, it even animates icon change properly even though we haven't implemented it. That's the behavior we get from React Native Paper's FAB out of the box.
@@ -918,12 +944,19 @@ export function DrawerContent(props) {
918944
```
919945
920946
Firstly, we get a current theme using `useTheme` hook from Paper. This means we can check `dark` property on it and pass the correct value to `Switch`.
921-
<br />Secondly, we pass a `toggleTheme` function to `TouchableRipple` to toggle theme whenever user presses a Switch.
947+
948+
<br />
949+
Secondly, we pass a `toggleTheme` function to `TouchableRipple` to toggle theme
950+
whenever user presses a Switch.
922951
923952
You should be able to toggle a switch now and both `Provider` from Paper and `NativeNavigationContainer` from React Navigation will automatically apply correct colors to the components.
924953
925954
<br />
926-
<img src="/assets/blog/using-react-navigation-5-with-paper/theming.gif" height="480" alt="Theming with React Navigation and React Native Paper" />
955+
<img
956+
src="/assets/blog/using-react-navigation-5-with-paper/theming.gif"
957+
height="480"
958+
alt="Theming with React Navigation and React Native Paper"
959+
/>
927960
928961
## Summary
929962

0 commit comments

Comments
 (0)