Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Remove void from possible MutationTuple promise generic #3334

Merged
merged 2 commits into from Aug 9, 2019
Merged

Conversation

hwillson
Copy link
Member

@hwillson hwillson commented Aug 9, 2019

void is left over from pre-launch mutate function experiments, and is causing grief when attempting to destructure promise-returned data from the useMutation mutate function. Goodbye void!

Fixes #3322.

`void` is left over from pre-launch mutate function experiments,
and is causing grief when attempting to destruture promise-returned
data from the `useMutation` mutate function. Goodbye `void`!

Fixes #3322.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why can mutate function of MutationTuple resolve to void?
1 participant