Michael R. Garfinkel
Michael R. Garfinkel
@kiropowered i wonder if `legacyMode: true` on create client would fix the issue. I'm on v4 but havent encountered dropped messages yet but ill keep an eye out. Most likely...
+1 in hoping that Azure Functions get support
Based on my testing and this: https://svelte.dev/tutorial/update I wouldn't merge this yet though. I've barely tested it outside of ensuring it fixed my use case. I wanted it created so...
Np, if your ok with it - I would like to add some playwright tests with a dummy sveltekit that runs through some sequences
been buried, should have time this week
@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
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...
dropped in ``` beforeUpdate(() => { console.log('key', key, this.resolveKey(key), options); this.use(key, onData, onError, { loadInitialCache: true, ...options, }) }); ``` and moved onData and on Error to be outside of...
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...
+1 seeing it myself as well