Skip to content

Commit 2752d30

Browse files
docs: clarify load parent() behaviour (#12655)
closes #12654 --------- Co-authored-by: Simon H <[email protected]>
1 parent 60e2296 commit 2752d30

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

documentation/docs/20-core-concepts/20-load.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -664,6 +664,7 @@ To summarize, a `load` function will rerun in the following situations:
664664
- It references a property of `url` (such as `url.pathname` or `url.search`) whose value has changed. Properties in `request.url` are _not_ tracked
665665
- It calls `url.searchParams.get(...)`, `url.searchParams.getAll(...)` or `url.searchParams.has(...)` and the parameter in question changes. Accessing other properties of `url.searchParams` will have the same effect as accessing `url.search`.
666666
- It calls `await parent()` and a parent `load` function reran
667+
- A child `load` function calls `await parent()` and is rerunning, and the parent is a server load function
667668
- It declared a dependency on a specific URL via [`fetch`](#making-fetch-requests) (universal load only) or [`depends`](types#public-types-loadevent), and that URL was marked invalid with [`invalidate(url)`](modules#$app-navigation-invalidate)
668669
- All active `load` functions were forcibly rerun with [`invalidateAll()`](modules#$app-navigation-invalidateall)
669670

0 commit comments

Comments
 (0)