Try router.refresh() instead of push

@European sprat

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

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

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

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

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

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

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

@European sprat

After getting a second to test it, using

window.location.href = `/movie/${movie.id}`

provides the required functionality withtout any need for attempts at revalidation