Oren Elbaum
Oren Elbaum
IMO not adding basic things like getters and setters would mean that this language will never get any significant adoption again, and even adding TS support won't help.
> > For now, I’m focusing on adding all of TypeScript’s features with mostly TypeScript syntax, except for type annotation which is `~` or `:=` instead of `:` (though `:`...
Yeah we are talking about build output.
This is the most idiomatic way: ```js import { createStore } from "solid-js/store"; const [state, setState] = createStore({ list: ["hello", "world"], newItemName: "New item", }); const addItem = () =>...
Yeah this is the easiest solution and I think that it's also slightly faster than stores although stores are more idiomatic.
It seems like the issue can be closed? The Vitest template seems to be working fine.
This is fixed now. Also is seems to be a duplicate of https://github.com/solidjs/solid-start/issues/24 Either way this issue can be closed.
It seems like the correction is happening when setting innerHTML. Is there a reason why we can't compare the innerHTML after setting it to the input html? i.e. ```js export...
What matters is that the structure stays the same right? So maybe we could parse the input html and the resulting innerHTML to see if they have the same structure?
Does it matter if we run it only in dev? It seems easier to do it this way than in compile time. It would be nice in compile time to...