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: versioned_docs/version-7.x/auth-flow.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ We want the following behavior from our authentication flow:
33
33
We can configure different screens to be available based on some condition. For example, if the user is signed in, we can define `Home`, `Profile`, `Settings` etc. If the user is not signed in, we can define `SignIn` and `SignUp` screens.
34
34
35
35
<TabsgroupId="config"queryString="config">
36
-
<TabItemvalue="static"label="Static">
36
+
<TabItemvalue="static"label="Static"default>
37
37
38
38
To do this, we need a couple of things:
39
39
@@ -449,9 +449,9 @@ In our component, we will:
449
449
450
450
So our component will look like this:
451
451
<TabsgroupId="config"queryString="config">
452
-
<TabItemvalue="static"label="Static">
452
+
<TabItemvalue="static"label="Static"default>
453
453
454
-
```js name="Signing in and signing out with AuthContext" snack version=7
454
+
```js name="Signing in and signing out with AuthContext" snack version=7 dependencies=expo-secure-store
If you have a bunch of shared screens, you can also use [`navigationKey` with a `Group`](group.md#navigationkey) to remove all of the screens in the group. For example:
Copy file name to clipboardExpand all lines: versioned_docs/version-7.x/handling-safe-area.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
@@ -328,7 +328,7 @@ To fix this you can, once again, apply safe area insets to your content. This wi
328
328
In some cases you might need more control over which paddings are applied. For example, you can only apply the top and the bottom padding by changing the `style` object:
Copy file name to clipboardExpand all lines: versioned_docs/version-7.x/navigating-without-navigation-prop.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ export function navigate(name, params) {
79
79
Then, in any of your javascript modules, import the `RootNavigation` and call functions which you exported from it. You may use this approach outside of your React components and, in fact, it works as well when used from within them.
80
80
81
81
<TabsgroupId="config"queryString="config">
82
-
<TabItemvalue="static"label="Static">
82
+
<TabItemvalue="static"label="Static"default>
83
83
84
84
```js name="Using navigate in any js module" snack version=7
85
85
import*asReactfrom'react';
@@ -237,7 +237,7 @@ For an example, consider the following scenario, you have a screen somewhere in
237
237
To avoid this, you can use the `isReady()` method available on the ref as shown in the above examples.
0 commit comments