You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/2018-02-06-react-navigation-1.0.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ tags: [release, announcement]
6
6
7
7
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!
8
8
9
-
<!--truncate-->
9
+
{/*truncate*/}
10
10
11
11
This release isn’t meant to be interpreted as a signal that React Navigation is “finished" — 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.
Copy file name to clipboardExpand all lines: blog/2018-04-06-react-navigation-2.0-rc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ tags: [release, announcement]
6
6
7
7
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.
Copy file name to clipboardExpand all lines: blog/2018-11-01-react-navigation-3.0-rc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ We are excited to announce the release candidate of version 3.0 today!
8
8
9
9
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).
10
10
11
-
<!--truncate-->
11
+
{/*truncate*/}
12
12
13
13
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.
Copy file name to clipboardExpand all lines: blog/2018-11-17-react-navigation-3.0.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The documentation is now live at [reactnavigation.org](https://reactnavigation.o
8
8
9
9
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).
10
10
11
-
<!--truncate-->
11
+
{/*truncate*/}
12
12
13
13
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.
Copy file name to clipboardExpand all lines: blog/2019-09-16-react-navigation-4.0.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The documentation is now live at [reactnavigation.org](https://reactnavigation.o
8
8
9
9
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.
10
10
11
-
<!--truncate-->
11
+
{/*truncate*/}
12
12
13
13
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.
Copy file name to clipboardExpand all lines: blog/2019-10-17-react-navigation-native.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ tags: [announcement]
6
6
7
7
React Navigation steps firmly into the next level and we’re very excited to announce to you something great happening in React Navigation codebase.
8
8
9
-
<!--truncate-->
9
+
{/*truncate*/}
10
10
11
11
## Make it custom
12
12
@@ -32,8 +32,16 @@ After years of growing development, we need to admit that we’re not always abl
32
32
33
33
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.
34
34
35
-
<imgsrc="/assets/blog/5.x/android-native-stack.gif"height="530"alt="Native Stack on Android" />
36
-
<imgsrc="/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
+
/>
37
45
38
46
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!
Copy file name to clipboardExpand all lines: blog/2019-11-04-using-react-navigation-5-with-ui-kitten.md
+30-7Lines changed: 30 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ tags: [tutorial, ui-kitten]
7
7
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!
8
8
In this blog post, we'll show a step-by-step guide on using React Navigation 5 with UI Kitten.
9
9
10
-
<!--truncate-->
10
+
{/*truncate*/}
11
11
12
12
## Introduction
13
13
@@ -17,7 +17,11 @@ The new React Navigation comes with several significant improvements such as [im
17
17
18
18
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.
19
19
20
-
<imgsrc="/assets/blog/using-react-navigation-5-with-ui-kitten/overview.gif"height="480"alt="React Navigation with UI Kitten Overview" />
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).
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.
alt="Drawer with components from React Native Paper"
317
+
/>
306
318
307
319
## Stack Navigator + Paper's Appbar
308
320
@@ -430,8 +442,10 @@ The Function that we pass to `header` prop has access to 3 properties:
430
442
431
443
Thanks to the **scene** property we can access the title of topmost screen on the stack and display it in the header.
432
444
**Previous** property tells us if there are any other screens lower on the Stack.
445
+
433
446
<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.
435
449
436
450
The thing that we haven't covered yet and it is very important is how to actually navigate between Stack Navigator screens.
437
451
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
456
470
457
471
Now, let's see what does the app looks like with Stack Navigator and Paper's Appbar.
458
472
459
-
<imgsrc="/assets/blog/using-react-navigation-5-with-paper/stack.gif"height="480"alt="Stack Navigator with React Native Paper's Appbar" />
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.
527
545
528
546
<br />
529
-
<imgsrc="/assets/blog/using-react-navigation-5-with-paper/bottom-navigation.gif"height="480"alt="Stack Navigator with Material Bottom Tabs" />
As you can see on the gif, the FAB button works in the same way as in a Twitter app.
751
777
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) {
918
944
```
919
945
920
946
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.
922
951
923
952
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.
924
953
925
954
<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" />
0 commit comments