Alex Lohr
Alex Lohr
`options.deferInit(initialize)` is somewhat of a foot gun IMO. If you don't read the instructions carefully, you'll easily break things. I think a boolean i option s fine for now. We...
There's still a pending review.
How about making it reactive in the client (on history change event)?
But in a composable way, so keep useUrl and add createUrl.
Claude still treats Solid as if it was React. Instead of returning the unsubscriber, you need to wrap it in onCleanup.
Since there are no reactive properties inside the effect, it is actually the same, but onMount is shorter, so go for it.
createHydratableSignal is only meant for signals that are supposed to have different initial values on the server and on the client during hydration. Since our signal should basically have the...
The initial value of `store2` is being immediately overwritten by the value from localStorage that is saved by the first persisted store with the name `x`. You can add new...
That's an interesting and valid argument and I will think about how to handle the issue. In the meantime, there's a workaround: Additional defaults would need to be added after...
Since the initialization is handled by createSignal/Store, there is nothing I can do about it. However, I can add a defaults value to the options that performs the same workaround...