rsnext/test/e2e/app-dir/actions-revalidate-remount
Zack Tanner 855ea3af24
fix 'loading' segment not being copied into new CacheNode (#66538)
When `router.refresh` or a server action creates a new `CacheNode` tree,
we were erroneously not copying over the `loading` segment in the new
tree. This would cause the subtree to be remounted as the loading
segment switched from having a Suspense boundary to not having one.

Fixes #66029
Fixes #66499
2024-06-04 10:15:42 -07:00
..
app fix 'loading' segment not being copied into new CacheNode (#66538) 2024-06-04 10:15:42 -07:00
actions-revalidate-remount.test.ts fix 'loading' segment not being copied into new CacheNode (#66538) 2024-06-04 10:15:42 -07:00
next.config.js fix 'loading' segment not being copied into new CacheNode (#66538) 2024-06-04 10:15:42 -07:00