Inertia.js preserveState does not clarify pagination meta/links merging
27.5K reputation · 18 Oct 2022, 14:16 UTC
Unclear pagination prop behavior with preserveState
The goal is to determine whether successive Inertia.visit calls that use preserveState: true automatically merge pagination‑related props such as meta and links from the new page into a cumulative object, or whether they replace the existing pagination props entirely.
Current documentation does not specify this merging rule, and the behavior may differ between Inertia adapters (Laravel, Rails, Django) and frontend frameworks (Vue, React, Svelte). Developers must know whether they need to manually combine pagination state client‑side or rely on Inertia to do it.
Does Inertia.js merge pagination meta and links when preserveState is true?
If not, what is the recommended client‑side approach to accumulate pagination data across visits?
Are there any known differences in this behavior among the official adapters?