Initialize currentUser
state in redux store when necessary
#17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a problem in current behavior:
currentUser
state is established in redux store. Authtoken is saved to local storage. Then it is load the component protected by<PrivateRoute>
.<PrivateRoute>
checks thatcurrentUser
is present in state and hasisLoggedIn
. So everything works.currentUser
state in redux store (unlessredux-persist
is used), even though the token is still in local storage. When<PrivateRoute>
tries to checkcurrentUser
, it can't find it. So it rejects the route.This PR is to initialize
currentUser
state in redux store from local storage upon page reload.This PR is to address #16