Include example/suggestions for local storage about redux-auth-wrapper

[mjrussell]

@mattkrick couple of thoughts there on local storage ^

[mattkrick]

You'll also need an authError state, because if both isAuth and isAuthing are false, you don't know whether the whole thing failed, or the whole thing hasn't started yet.

[mjrussell]

Yup good call, luckily this is a common pattern for redux actions and should be familiar with most people i.e. LOGIN_SUBMITTED/FAILED/SUCCESS for constants

[eMerzh]

good idea, and if you got a logout exemple i'll be interested as well :)

[mjrussell]

See #35 for an ability to display a component while asynchronously performing the login request

[johnwiseheart]

My suggestion for this is using local storage in the action for LOGIN_SUCCESS/LOGOUT_SUCCESS as well as the initialState for the auth reducer:

In LOGIN_SUCCESS, you do something along the lines of:
localStorage.setItem('jwt_token', response.token)

Then in LOGOUT_SUCCESS, you clear the item:
localStorage.removeItem('jwt_token')

and finally in the initialState for your auth reducer:

const auth = (state = {
    isAuthenticated: localStorage.getItem('jwt_token') ? true : false
}, action) => {
...

Obviously you could do a similar thing for other implementations of auth that aren't JWT.

This way, you can persist login on refresh. Thoughts?

[mjrussell]

@johnwiseheart yup I think that should work pretty well. You could also go one step further and use a setTimeout or kick off a saga to clear the token locally and clear the auth reducer if the token or cookie has an expiration date. Seems to me that the necessary features for this are probably all set, just want an example since its a common use case