How to opt-out of re-triggering page-level resources after server action invocation
I'm wondering if I can opt-out of the default behavior of re-triggering page-level resources created with createAsync and cache after a server action invocation. I want more control and explicitly opt-in to cache invalidation. Is this possible with SolidStart or solid-router? For example, in the code below, loadHelloWorld is being executed after each submission of runServerAction even though no cache invalidation is required as the data on the page will not change as a result of the server action.
2 Replies
See if a
reload()
with an option of {revalidate: []}
at the end of the action changes things.
https://discord.com/channels/722131463138705510/1243132814170394644/1243558850892795970@peerreynders thank you! Unfortunately the page resources still re-run when I have: