S
SolidJS•12mo ago
oneiro

Solid-start client side state best practices

Hey folks, I noticed that the docs are still missing the section on the various kinds of application state. Therefore I wanted to ask here what is considere to be a good approach to handle state after hydration. Example: We use createServerData to build our initial route data. But after hydration we would like to have the state globally available. What would be the best approach to do this? Should we simply take the data and put it in a store or is there another recommended approach? Thanks in advance
2 Replies
oneiro
oneiro•12mo ago
oooh, I just realized that there is useRouteData() to consume routeDate inside components. So I probably don't even need an extra store to manage the state
Alex Lohr
Alex Lohr•12mo ago
Other than that, you can use all of solid's reactive system to manage your state however you like.
Want results from more Discord servers?
Add your server
More Posts
Solid-start-vercel rollup errorHey, I am trying to build my solidstart app with solid-start-vercel package included (it works just Not sure whether I'm using reactivity right... (Codereview)Ok so I recently ported my personal project to Solid coming from React, and while I did it I kind ofHow to improve performance in my code?```js const CompareStats = () => { const [shown, setShown] = createSignal<Element[]>([]); consfetch in createEffect?When a set of conditions are satisfied on some state, I want to execute an http request to the serveCoordinating Signals in a Layout SystemHi all, I'm trying to implement a layout system in SolidJS that works similarly to mobile frameworksSignals not updating in <For> tagI have code that looks like this: ```jsx const [grid, updateGrid] = createSignal(new Array(10).fill(