formal steppe
If you imagine a really simple server component page that awaits some function that returns data from the DB, how do I ensure the data is fresh? e.g., user account page, user makes edit, leaves, comes back, sees stale original data.
I think I want the concept of "pre-rendered", but I'm finding that client-side state is clobbered every time this server rendered page is re-mounted
sterile ibex
If you imagine a really simple server component page that `await`s some function...
Use router.refresh() or client-side data fetching libraries
In a few months the app directory will have built in support for mutation, then it will be much simpler
formal steppe
sterile ibex
https://nextjs.org/docs/api-reference/next/router#routerreload router.reload?
That documentation does not apply to the app directory
formal steppe
this makes it awkard if another page alters the underlying data (because refresh doesn't look to take a URL argument), but it sounds like if I have a client-component inside my server component, I just need a useEffect(() => router.refresh(), [])
beautiful tyvm @sterile ibex, I think this is what I was looking for last night but was too poor at phrasing
sterile ibex
this makes it awkard if another page alters the underlying data (because `refres...
Mutation support for the app directory is very poor right now yeah
Although improvement is coming, we have some teasers on twitter as well
formal steppe
@ what handle?
is NextRequest available to the server component at all? I'd like to reuse helpers I made for my API but they're all req based
sterile ibex
@ what handle?
Forgot where it is, but it’s something like each fetch is marked with a key and you can do revalidate(key)
sterile ibex
is NextRequest available to the server component at all? I'd like to reuse helpe...
No afaik