Properly decode partialOperationContext in all hooks and components. Update api.md to reflect latest changes to the reason-urql API. #142
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 is the last PR before we release v1.5.0 of
reason-urql
🎉 The core change here is that we properly decode apartialOperationContext
into a format thaturql
can understand. The key part here is that we exposerequestPolicy
as a polymorphic variant on the Reason side, so it needs to be properly decoded into its JS string representation before it can be sent tourql
.I also updated the
api.md
file to more accurately reflect the current state of the API. That was in a bit of rough shape, so I want to continue improving it over the coming releases, or at least break it up into more manageable chunks.This will be the last release we do before the migration to BuckleScript 7! That's going to get rid of so much of the
[@bs.deriving abstract]
nonsense we currently have to do. Pure record to object support will be so great! That, alongside a migration tourql
1.4.0, will form the basis of either1.6.0
(if changes to the API are minimal) or v2 (if they're more involved).