Add user context flow and fix bugs #2
Merged
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.
Description
This PR fixes some bugs and improves the CheckAuth component, but most notably refactors the app to utilize Context for the user. This change simplifies some of the logic we had before and allows any component to access the current user data like this:
Possible
user
states from UserContextuser
will be null (meaning the context isn't ready to use)user
will be the CognitoUser object (a user is authenticated)user
will be:{username: false}
(no user is authenticated)Notes
We could tidy this up a bit by wrapping the CognitoUser object so it always has a
status
representing loading, authenticated, unauthenticated, etc. See the refactored CheckAuth component for an example of current usage.I think it would be a little more readable if we wrap it to provide a standard
status
column.