Revalidation and Cache Invalidation on Dynamic Path | Next.js | Page 1

sturdy emberBOT Jul 23, 2023, 9:42 PM

#

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

      🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in <id:customize>

      ✅ You can mark a message as the answer for your post with `Right click -> Apps -> Mark Solution`
      (if you don't see the option, try refreshing Discord with Ctrl + R)

humble mortar Jul 23, 2023, 10:29 PM

#

Try router.refresh() instead of push

oblique crater Jul 23, 2023, 10:31 PM

#

@humble mortar

That would refresh the page at /movie/[movieID]/review

#

The page at /movie/[movieID] is the one I need revalidated 😦

humble mortar Jul 23, 2023, 10:32 PM

#

Ah sorry I thought it was sent back to the same page

oblique crater Jul 23, 2023, 10:48 PM

#

I suppose I could turn the form into a modal and do a refresh, but I feel like next has this functionality with an api route for revalidate

humble mortar Jul 24, 2023, 12:15 AM

#

I think the issue is router push and replace so client soft navigation which doesn't refetch data, you can read a bit more about it here https://nextjs.org/docs/app/api-reference/functions/use-router

I actually ran into a similar issue with my app and ended up using react query in RSC and client components to keep things up to date

Functions: useRouter

API reference for the useRouter hook.

#

Alternatively I think you can use effect the pathname and so a router refresh

oblique crater Jul 24, 2023, 12:24 AM

#

Someone else stated that setting the href on window does a hard navigation that would solve it elsewhere, but I havnt been able to test it

#

Other idea is to add an artifical but unneeded query to the url for the push

#Revalidation and Cache Invalidation on Dynamic Path