feat: Implement User Data Persistence with Encrypted Cookie #155
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
bdca0ec to
03a830f
Compare
03a830f to
4a4dcc5
Compare
alexcasalboni
approved these changes
Dec 20, 2024
KokaKiwi
approved these changes
Dec 20, 2024
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.
Checklist
Description of Changes
We need to implement user data persistence through an encrypted cookie (edgee_u) to maintain user context across sessions. When a user event is fired, the user data should be stored in an encrypted cookie, and this data should be retrieved and added to the user context for subsequent events.
This PR follows the requirements and technical details of #154
I improved the documentation at the same time, which was not up to date in the scripts I worked on.
Related Issues
#154