Don't understand why it's not easier to refresh server data.
Unanswered
Tomistoma posted this in #help-forum
TomistomaOP
This GitHub issue shows a massive demand for making server data refresh easier: https://github.com/vercel/next.js/discussions/49345 bottom comment has 42 upvotes.
I have root page / that POSTs to /api/saved-location , creates a DB entry, and I even try revalidatePath("/saved"). I have a <Link> to /saved Server Component page where users should be able to view the latest saved location, but it still needs a browser refresh... I don't want a router.refresh() on root / because it's a heavy page. I don't understand why this common case isn't simple to just ensure /saved Server Component has a refresh. export const dynamic = "force-dynamic"; doesnt work either
I have root page / that POSTs to /api/saved-location , creates a DB entry, and I even try revalidatePath("/saved"). I have a <Link> to /saved Server Component page where users should be able to view the latest saved location, but it still needs a browser refresh... I don't want a router.refresh() on root / because it's a heavy page. I don't understand why this common case isn't simple to just ensure /saved Server Component has a refresh. export const dynamic = "force-dynamic"; doesnt work either