Skip to content

Commit 5e6e25e

Browse files
committed
Remove reference to isSignout state that doesn't show up anywhere
1 parent 5b36bbe commit 5e6e25e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

versioned_docs/version-7.x/auth-flow.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -288,7 +288,7 @@ return (
288288
);
289289
```
290290

291-
In the above snippet, `isLoading` means that we're still checking if we have a token. This can usually be done by checking if we have a token in `SecureStore` and validating the token. After we get the token and if it's valid, we need to set the `userToken`. We also have another state called `isSignout` to have a different animation on sign out.
291+
In the above snippet, `isLoading` means that we're still checking if we have a token. This can usually be done by checking if we have a token in `SecureStore` and validating the token.
292292

293293
Next, we're exposing the sign in status via the `SignInContext` so that it's available to the `useIsSignedIn` and `useIsSignedOut` hooks.
294294

@@ -350,7 +350,7 @@ return (
350350
);
351351
```
352352

353-
In the above snippet, `isLoading` means that we're still checking if we have a token. This can usually be done by checking if we have a token in `SecureStore` and validating the token. After we get the token and if it's valid, we need to set the `userToken`. We also have another state called `isSignout` to have a different animation on sign out.
353+
In the above snippet, `isLoading` means that we're still checking if we have a token. This can usually be done by checking if we have a token in `SecureStore` and validating the token.
354354

355355
The main thing to notice is that we're conditionally defining screens based on these state variables:
356356

@@ -360,7 +360,7 @@ The main thing to notice is that we're conditionally defining screens based on t
360360
Here, we're conditionally defining one screen for each case. But you could also define multiple screens. For example, you probably want to define password reset, signup, etc screens as well when the user isn't signed in. Similarly, for the screens accessible after signing in, you probably have more than one screen. We can use `React.Fragment` to define multiple screens:
361361

362362
```js
363-
state.userToken == null ? (
363+
isSignedIn ? (
364364
<>
365365
<Stack.Screen name="SignIn" component={SignInScreen} />
366366
<Stack.Screen name="SignUp" component={SignUpScreen} />

0 commit comments

Comments
 (0)