Skip to content

How can I separate cache operations and side effects in a custom mutation hook? #276

You must be logged in to vote

I just published a fix for this. My original intention was the functionality you are describing, so I consider this a bug. In the latest version, if both options are defined, they will both fire with the mutate-level handler first, then the hook-level handler.

Replies: 2 comments 4 replies

You must be logged in to vote
0 replies

You must be logged in to vote
4 replies
@denisborovikov

@denisborovikov

@tannerlinsley

@denisborovikov

Answer selected by tannerlinsley
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants