(re)trigger the load function

Is your feature request related to a problem? Please describe. The new invalidate(href) feature in $app/navigation is a great way to trigger the execution of a load function that works in most cases. The problem is that this only works if one uses the fetch function that is provided as an argument to load. If a apiClientWrapper is used this does not work anymore.

Describe the solution you’d like One solution would be to pass a invalidate or update function to the load so that I can be passed as a prop or via context. This solution would update a specific load function instead of a specific fetch url.

<script context="module">
import { api } from '$lib/myapi';
export async function load({page, update}){
    const item = await api.getItem(page.params.id);
    return { 
        props: { item, update }
    }
}
</script>

<script>
import Item from '$lib/Item.svelte';
export let item;
export let update;
</script>

<Item {item} />
<button on:click={update}>Reload</button>

Describe alternatives you’ve considered A alternative would be to write a second function in the (non module) script tags that replicates the load function to update data.

How important is this feature to you? Somewhat important. It would make the code cleaner and more reusable but there are easy workarounds.

[icalvin102]

@etienneburdet goto() will only run load() if page.params, page.path, page.query, session or context is used inside of load and one of those values has changed since the last run of the load function. This is the desired behavior of goto or any form of navigation as this prevents unnecessary loading of (sub)routes.

What I want is function that is similar to invalidate but it should be bound to a load function instead of invalidating a URI.

The use case is similar to the one described in #1277 but with a more general solution.

[lemmon]

Perhaps something like?

goto(href, { replaceState: true, invalidate: true })

There are still many different use cases when you want invalidate page data only or invalidate both page and layout altogether. Anyway, the invalidate function seems to be no good when you use custom fetch() lib.