Send revalidated data alongside mutation in tRPC

Hi. How would I go about sending new data from my server when there is a mutation made? I have a query that fetches posts and it seems useless to send a mutation and once that mutation succeeds, send a new request for all new posts. Is there realistically an option to re-send the posts from the server alongside the mutation with some tRPC magic, so that it gets new state quicker? Or how should I architect this?

oof2win2OP•5/26/23, 1:48 PM

like realistically a user shouldn't have more than say ~1s delay at most from mutating to getting the new data back but i mean if i could reduce that it would be nice

cje•5/26/23, 2:47 PM

you have two options roughly speaking

cje•5/26/23, 2:47 PM

invalidate after the mutation completes, possibly with optimistic ui prior to that

cje•5/26/23, 2:47 PM

manage cache manually

cje•5/26/23, 2:49 PM

whatever you return from a mutation is available in its onSuccess (so you could manually update the cache once your mutation is successful)

cje•5/26/23, 2:50 PM

but i generally find that to be the wrong approach as it goes into manual cache management, which is a place you probably don't want to be

cje•5/26/23, 2:50 PM

better: optimistically update the UI in onMutateonMutate , invalidate the query in onSettledonSettled

cje•5/26/23, 2:51 PM

that way you DO completely refetch the query, but:

you're showing updated UI as soon as the user clicks a thing
if your manual cache invalidation ends up being incorrect, it gets fixed once the onSettledonSettled callback runs

oof2win2OP•5/26/23, 6:18 PM

yeah manual cache management isnt what i want tbh

oof2win2OP•5/26/23, 6:19 PM

thanks

Send revalidated data alongside mutation in tRPC

Similar Threads

Similar Threads

Similar Threads