remote query without await

[hendrik-huels]

Describe the bug

I don't know if this is intended, but it feels unintuitive.

This does not fetch:

<script lang="ts">
	import { getPosts } from './data.remote';

	const query = getPosts();
</script>

This does:

<script lang="ts">
	import { getPosts } from './data.remote';

	const query = getPosts();
	query.loading
</script>

It seems like you have to access loading, current or error to trigger the fetch of the RemoteQueryFunction.
I created a little repo to showcase how i try to preload stuff for a component.

I would assume, that calling getPosts() would already start fetching.

Reproduction

https://github.com/hendrik-huels/bug-or-feature

Logs

System Info

tested on "@sveltejs/kit": "^2.63.0" and "@sveltejs/kit": "3.0.0-next.11"

Severity

annoyance

Additional Information

No response

[elliott-with-the-longest-name-on-github]

Yeah, this is some behavior we'd like to get rid of (and I think we're getting close to being able to right now). The problem we had in the past is that you need to be able to construct a query to refresh or set that query, eg. get_user(1).set(...). Obviously in this case, you don't want the query to fetch after get_user(1), because you're immediately setting it.

The idea we've toyed around with in the past has been to fetch after a microtask if you haven't accessed any of the "I want to update this" properties. I can't remember why it wasn't working at first -- something to do with hydration maybe -- but I think the barriers to that might be gone now, so it might be as simple as implementing it.

[jjones315]

i actually intentionally do this in a few places in my app.

<script>
    const usersQuery = $derived(getUsers({ someParamsIDontWantToCalculateEverywhere: foo, ... }));
    let open = $state(false);
</script>


<Button isLoading={open && usersQuery.loading} onclick={...}>
    Open Modal
</Button>

<svelte:boundary>
    <Modal bind:open>
        {const users = await usersQuery}
        ... things with users
    </Modal>
</svelte:boundary>

would there be a way to opt to create a queryable without executing it?

[elliott-with-the-longest-name-on-github]

Right now no, there wouldn't be. The other idea I've been toying with is giving queries some sort of immediate or execute method that just returns the query instance, so that you can do something like this:

<script lang="ts">
	import { getPosts } from './data.remote';

	const query = getPosts().immediate();
</script>