-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
(graphcache) - Reimplement default-storage serializer/deserializer #866
Conversation
🦋 Changeset is good to goLatest commit: 0d11c8f We got this. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Awesome 💯
826aecf
to
bf9fcd1
Compare
bf9fcd1
to
0d11c8f
Compare
I can't wait to try it! |
Tried with codesandbox tar package. IT WORKS!!! :) |
Will you release soon? |
Resolve #864
Summary
This fixes an issue where deleted values wouldn't be persisted correctly, since the
default-storage
serializer coerced bothnull
andundefined
to"null"
JSON values. The@urql/exchange/default-storage
implementation now comes with a new serializer which is incompatible with the old one but should be faster and more correct. It's incompatible with the old one, so the defaultidbName
has been bumped tographcache-v4
.Set of changes
data.persist
setdefault-storage