User authentication flow
A change was introduced recently into components/AuthWrapper.js
that is messing with the way it's being used in HHMI
- line #47 is expecting a logged in user in order to remove the spinner
- we're using AuthWrapper to try to authenticate the user, but not necessarily block them from seeing the content of the page. The use case is for public pages that still need to show when the user is signed in (a user menu on the header instead of a log in button), or that offer extra features for logged in users. To make the pages available only to logged in users we use
RequireAuth
- this change is blocking visitors from viewing a public page, unless they're signed in
Should I create a MR to remove it? Does it affect the usage in other projects? Is there any other way to handle the use case described above?