Alex Lohr
Alex Lohr
Internal changes are already reactive. The next step is to support a tauri file watcher (supported since v2).
That's a pretty great idea. Thanks!
But equals by definition compares the last value to the next one. As there is no last value initially, you would have to guard your comparison against it being undefined....
createMemo cannot know if you are intending to use the initial value or not.
This was merely an answer to your statement that having an initial value was pointless if you're not using it. But that's merely your preference based on a single case....
This is a known issue. If we want to use the internal spread (which minimies code and development effort), we can't do anything about it.
Unfortunately, running with the owner creates the exact error in hydration that we aim to solve with using the timeout.
We do not know if the server and the client will have access to the same data on their storage. You could also using the sync API or cookieStorage to...
There is no way for us to know on either server or client what data the other side will have unless we either sync them manually or deliberately let them...
OK, I switched to your suggested solution.