ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #inertiajs
Context Inertia.js partial reloads via Inertia.visit({ only: [...] }) perform a shallow merge at the top level of page props. When a requested prop contains nested objects, the entire nested structure is replaced rather than deeply merged. This behavior is documented but leaves developers without a built-in strategy for preserving unrelated nested fields dur
InertiaJS allows server-side flash data to be passed to the client via the $page.props.flash object. This mechanism is intended to provide one-time notifications following a redirect or a specific server action. When utilizing router.visit() with preserveState: true , the client-side page object retains its current state. Because partial reloads do not autom
Goal: determine whether the `only` filter applied during a partial reload also limits shared middleware data and whether lazy or deferred props are treated as already requested when omitted from `only`. Constraints: the `only` option is scoped to a single request, does not persist across full navigations, and its interaction with lazy props (evaluated on dem
Precise goal Determine whether Inertia.js can guarantee that props wrapped in Inertia::lazy() or Inertia.lazy() are never serialized into the initial #page script tag under any rendering mode. Constraints and uncertainty The framework documentation warns against placing sensitive data in props and recommends lazy evaluation as mitigation. However, lazy props
Uncertainty About Shared Data Merging in Concurrent Scenarios Inertia.js exposes a shared data feature that automatically injects specified key/value pairs into every page response. The library merges these shared entries with page‑specific props before rendering. However, the documentation does not specify how this merge behaves when multiple concurrent req
Goal Determine how Inertia.js should behave when a server framework (e.g., Laravel) returns a 302 status code together with a valid Inertia JSON payload that includes a redirect key, and how the various client adapters (Vue, React, Svelte) interpret that response. Constraints & Uncertainty The official documentation states a 200 status is required for a
react
laravel