Dependent fetching just doesn't work? about sswr

[ekzhang]

Unfortunately I don't have a replication at the moment, but the error might have to do with the fact that onMount is called in the constructor? If useSWR is reactively called behind a $: in the dependent fetching scenario, then it would be rerun later in the component lifecycle after the mount has already happened.

[ConsoleTVs]

A lot of people seem to be getting this as well. Will investigate.

[mgarf]

@ConsoleTVs was this ever fixed? i feel like i'm seeing the error and before i dig deeper wanted to check if maybe its still outstanding issue

[ConsoleTVs]

It might be. I am in the process of updating the underlying library of both, sswr and vswr. Althought this seems to be related to svelte itself, this library is around 70 LOC specific svelte code. It should not be hard to spot either if you want to help!

Also, could somebody post a replication code on codesandox?

[mgarf]

i might have some time today to dig into this. though im in the early stages of learning svelte, most of my framework knowledge is react, 🤷 doesnt hurt to try

[mgarf]

dropped in

    beforeUpdate(() => {
      console.log('key', key, this.resolveKey(key), options);
      this.use<D, E>(key, onData, onError, {
        loadInitialCache: true,
        ...options,
      })
    });

and moved onData and on Error to be outside of on mount. The good news is that the fetching is now fixed. the problem is we are creating waaay to many subscriptions... so just need to find the underlying refetch for this.use that i can use on the existing subscription

[mgarf]

ok removed my changes and replace onMount with beforeUpdate and added an if condition to check if the subscription has been created. @ekzhang was right the onMount is happening too early

    beforeUpdate(() => {
      // Handlers that will be executed when data changes.

      // Subscribe and use the SWR fetch using the given key.

      if (!unsubscribe)
        unsubscribe = this.use<D, E>(key, onData, onError, {
          loadInitialCache: true,
          ...options,
        }).unsubscribe
    })

I'll create a PR for the above change but I'm not a huge fan of it since it seems hacky. Going to also do some extra testing as well to make sure it doesn't have some weird side effects

[eytanProxi]

Still doesn't work ... 😢

[ConsoleTVs]

@eytanProxi can you manually test this branch? If it works I can merge it: #33

[eytanProxi]

@ConsoleTVs : I tried the fix but the bug is still here.
Should we move to TurboQuery ?

[ConsoleTVs]

I have no idea how to fix that. You can give turbo query a shot, it is basically using Promises. Should be easy to create a small adapter. I am pushing turbo query beyond with vue and specially solidjs as a replacement for this...

[smblee]

@ConsoleTVs are you referring to https://github.com/StudioLambda/TurboQuery?