SolidStart render page from POST function
SolidStart with method="post" and action="".
To validate the form on server side, I export a POST function.
However I am wondering how I could, if the data I got isn't valid, show the form again with the data the user already submitted (and maybe additional error messages) from this POST function?...How to update nested store values such that it triggers updates
How to have data attribute on Custom component?

createStore from fetched data ?
losing reactivity in For component
todo.nested.data not updated when i set the store?...`xyz` is not a function
I have too long Switch, Match

Can we use solid's For and Index component for data that isn't stored as a signal?
For and Index components with this approach?Property 'giscus-widget' does not exist on type 'JSX.IntrinsicElements'

SSR Performance (SolidJS vs Next)
wrk benchmark on a project initialized with npm init solid and npx create-next-app@13 and found the following numbers. The Next.js front page is 3.11 kB in size and the one from solid is only 1.78 kB. Both projects were started using npm start.
Solid Router Layouts
Is this considered good practice?
params.id and isEditMode are active. My question. Is this considered a good practice?
My component has 2 modes. Create and Editing. I'm trying to combine both into one view. Is it good practice to create 2 api fetches from a createResource and conditionally handle what the output is in a createEffect?
I would love some feedback on the code below and maybe explain if this is a good approach....how to use from or reconcile with an external producer
addTodo() with a commit to the external store.
The store seems to produce data just fine. This is the console output from the subscribe callback below (After I created the first todo from the frontend)....
Export an IIFE build with esbuild not working as expected
SVG path animation in Solid like Svelte's transition draw
Getting User Info from route page
How to properly type the `mergeProps` with Typescript?
mergeProps function to enter some default props for my component, but this is causing a Typescript error because some properties that are using string literals are being replaced with just type string.
```ts
interface ButtonBaseProps extends JSX.ButtonHTMLAttributes<HTMLButtonElement> {
variant?: ButtonVariant;...reactive initialValue on createResource
Can I create a hole in Suspense
Is the on change broken for file inputs?