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
Once the client has received this prop, subsequent requests will skip resolving the callback entirely and the prop will be excluded from the response. The client will automatically reuse the remembered value.
17
+
After the client has received this prop, subsequent requests will skip resolving the callback entirely and the prop will be excluded from the response. The client will automatically reuse the remembered value.
18
18
19
-
Keep in mind that navigating to a page that doesn't include the once prop will break the chain. The backend will resolve the prop again when you navigate to a page that includes it.
19
+
Navigating to a page without the once prop will break the chain, and the prop will be resolved again on the next page that has it.
You may set an expiration time using the `until()` method. This method accepts a `DateTimeInterface`, `DateInterval` instance, or an integer number of seconds. The prop will be refreshed on a subsequent visit after the expiration time has passed.
69
+
You may set an expiration time using the `until()` method. This method accepts a `DateTimeInterface`, `DateInterval`, or an integer (seconds). The prop will be refreshed on a subsequent visit after the expiration time has passed.
You may assign a custom key using the `as()` method. This is useful when you want to share data across multiple pages while using different prop names.
Both pages share the same underlying data because they use the same custom key. The prop will only be resolved once, even though the prop names differ.
93
+
Both pages share the same underlying data because they use the same custom key, so the prop is only resolved for whichever page you visit first.
0 commit comments