Removing this will simplify the onboarding and UX
Currently if a user visits the app on a browser that was previously logged in and now has the session expired, they'll see an alert that says "Login required, cuz security". When they press OK, they'll be redirected to the login page. We should replace this with a component in the sidebar that indicates that they are no longer syncing events to Google, and encourage them to reconnect their google calendar.
implementation
Remove the /login route.
Handle google auth expirations
- Google API token will expire. In the past, we forced the user to re-authenticate by going to the /login page
- Now we should just prompt the user to re-authenticate from whatever view they're on
- If they continue using the app as normal, just save their data in indexeddb and warn them that they'll need to reauthenticate before the changes can be synced back to their gcal
Replace this with an auth param auth=logout to stay consistent with the current auth flow
context
depends on #1404
loaders.ts
Removing this will simplify the onboarding and UX
Currently if a user visits the app on a browser that was previously logged in and now has the session expired, they'll see an alert that says "Login required, cuz security". When they press OK, they'll be redirected to the login page. We should replace this with a component in the sidebar that indicates that they are no longer syncing events to Google, and encourage them to reconnect their google calendar.
implementation
Remove the /login route.
Handle google auth expirations
Replace this with an auth param
auth=logoutto stay consistent with the current auth flowcontext
depends on #1404
loaders.ts