You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+81-8
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,9 @@ Feel free to contribute to the project by creating issues or pull requests.
24
24
-[Features](#features)
25
25
*[Shared data](#shared-data)
26
26
*[Flash Messages](#flash-messages)
27
+
*[Deferred props](#deferred-props)
28
+
*[Merging props](#merging-props)
29
+
*[History encryption](#history-encryption)
27
30
*[Server-side rendering](#server-side-rendering)
28
31
*[Vite helper](#vite-helper)
29
32
-[Examples](#examples-1)
@@ -203,6 +206,83 @@ public async Task<IActionResult> Destroy(int id)
203
206
}
204
207
```
205
208
209
+
### Deferred props
210
+
211
+
Deferred props allow you to defer the loading of certain page data until after the initial page render. (see [Inertia.js docs](https://v2.inertiajs.com/deferred-props))
212
+
213
+
In the example below, the `Posts` prop will be loaded after the initial page render.
> Deferred props are supported starting from Inertia.js v2.0
231
+
232
+
233
+
### Merging props
234
+
235
+
By default, Inertia overwrites props with the same name when reloading a page. However, there are instances, such as pagination or infinite scrolling, where that is not the desired behavior. In these cases, you can merge props instead of overwriting them. (see [Inertia.js docs](https://v2.inertiajs.com/merging-props))
0 commit comments