feat: add bindings for @urql/exchange-persisted-fetch and @urql/exchange-refocus #251
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.
This PR adds bindings for two more exchanges 🎉:
@urql/exchange-persisted-fetch
@urql/exchange-refocus
The diff is a touch wonky because I did some additional reorganization, including organizing exchanges alphabetically in source, tests, and docs. Rest assured, there were no changes to any of the other recently bound exchanges, just moving them around.
With respect to the
persistedFetchExchange
, I left out a more extensive binding forDocumentNode
in favor of a type parameter, because a fullDocumentNode
binding is way outside the scope of this library. This way, users can annotate the node for the access pattern they have (be itdocument.documentId
or something else).