Resolving Chicken-Egg Issue with Cache During Login Session Storage and Token Retrieval
i think im having a chicken-egg issue with the Cache. when i log in, a session is stored in local storage. on log in a user is immediately directed to a home route who's route loader leverages a cache that
1. retrieves session from local storage
2. extracts tokens
3. returns tokens
with the expiry derived from the accessToken.
when the login effect finishes the last thing it does is add the session to storage before being redirected to the home page. but on initial load the loader for the home page returns undefined for the tokens, and by extension an undefined Bearer token for my api...
1. retrieves session from local storage
2. extracts tokens
3. returns tokens
with the expiry derived from the accessToken.
when the login effect finishes the last thing it does is add the session to storage before being redirected to the home page. but on initial load the loader for the home page returns undefined for the tokens, and by extension an undefined Bearer token for my api...
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
