nextjs - 💡(How to fix) Fix App Router: route groups prefetch cache should isolate parallel slots [1 participants]

TL;DR

The most likely fix involves updating the route cache key path to include the parallelSlot identifier to ensure isolation per parallel slot.

Guidance

• Review the correction branch linked in the issue for the specific changes made to the route cache key path to include parallelSlot.
• Verify that the parallelSlot identifier is correctly incorporated into the cache key to prevent sharing across route-group/parallel-slot contexts.
• Test the scenario with the updated cache key to confirm that back/forward navigation restores the correct tree for each parallel slot.
• Check for any potential cache key collisions or issues with the updated implementation.

Example

No explicit code example is provided due to the lack of specific code details in the issue, but the correction branch should contain the necessary changes.

Notes

The fix relies on correctly identifying and incorporating the parallelSlot in the route cache key path, which may require careful review of the cache implementation and the correction branch.

Recommendation

Apply the workaround by incorporating the parallelSlot identifier into the route cache key path, as this should isolate cache entries per parallel slot and resolve the issue with shared cache entries across contexts.