Creating user session token on-demand #4917
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
💙 vsf-next-demo successfully deployed at https://4472fa207af64dab237e1ba82bf8447505876df5.vsf-next-demo.preview.storefrontcloud.io |
filrak
requested changes
Sep 25, 2020
filrak
requested changes
Sep 28, 2020
|
Ref: #4927 |
filrak
approved these changes
Sep 28, 2020
filrak
reviewed
Sep 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We used to create an anonymous token (user session) each time user visited the page which can end up with so many opened user sessions.
This PR introduces creating that token only on-demand when we really need to open user session eg. when we interact with the cart or user profile
┆Issue is synchronized with this Jira Story by Unito