Signal Factories and eslint warnings
How to handle Reactivity for nested objects?
updateTree(node, id) the tree will update from that node (including) and outward the branch, meaning all nodes after that node needs to be updated/rerenderd.
Below is some simplified example code.
Thank you
...Replace part of string with a component
Just wondering if anyone has done anything similar with solidJS. It's probably pretty niche....
Can the server$ call get access to the Request object?
createServerAction$(async (form: FormData, { request })
createServerAction$(async (form: FormData, { request })
Store for binary tree object
Solid-Slider docs
details in the createSlider destructuring is used for. Doesn't seem to be reactive.
Was wondering where I could get the length of initialized slides....SolidJS + DenoDeploy
Reactivity does not flow through nested structure and <For />
useRouteData returning undefined
Show or doing if (!students) return; but that causes hot module reloading to not work at all because I think it's never actually loading properly client side
```ts
import { For, Accessor, createResource } from 'solid-js';
import { useRouteData, createRouteData } from 'solid-start';...
Nested ErrorBoundary not used
Are there any performance implications with using the style prop?
Losing reactivity in production build due to multi-project setup lib <--> app
createEffect() is not being triggered. Everything works as expected as long as I use the vite command. But when I use vite build && vite preview it does not work anymore. The createEffect is only ever triggered once and subsequent accesses of the signal do not trigger it anymore. How can I debug such a case?page not found when navigating to routes
A tag. I also can't find a solution in the actual github page from solid-start. is there a solution to this? thx!!
p.s. this is only replicable on localhost dev environment, but when i attempted to do npm run build and npm start, it does not occur....
solid-transition-group leads to reactivity warning inside test cases
<Transition />-component is present, all of our test cases start throwing the computations created outside a createRoot or render will never be disposed- error.
If we remove the transition the error disappears. Any idea what could cause this?...If I'm using createResource, why would I use Suspense?
Can you use the reactive object from useSearchParams as a source signal for createResource?
Issue with event delegation and a native library
Search params reactivity in route's data loader function

How to pass key into createRouteData function inside useRouteData ?

Context is undefined during development reloads
const useAppState = () => { return useContext(AppContext)! }
const useAppState = () => { return useContext(AppContext)! }