-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Allow setting custom storage engine per atom #30
Conversation
Todos for this PR:
|
Update limit to track the current progress in diff. |
Looks good. Rebase to new |
I have just noticed, that I forgot about |
@@ -43,6 +43,21 @@ test('saves to localStorage', () => { | |||
equal(events, ['1', undefined]) | |||
}) | |||
|
|||
test('saves to a custom storage', () => { |
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.
We need to test that didn’t change default storage engine
I tried to merge it and fix Maybe we need another API for that. |
Closes #27
This is my shot at implementing a custom engine per atom. My particular use case: using one store in
localStorage
and the other insessionStorage
.