-
Notifications
You must be signed in to change notification settings - Fork 0
chore: do not share data between memory sessions #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
KnorpelSenf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to avoid structuredClone?
|
oops |
KnorpelSenf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's certainly an interesting decision to clone all values passed to the storage adapter, too. #4 only mentions memory sessions because they live in RAM and traditionally share data between requests. Usually, I'd expect persistent storage adapters to serialise the data anyway, making your cloning redundant.
What was the reason for this decision?
KnorpelSenf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Closes #4