Question: Why are you using Solid's createMutable?

I wasn’t sure if I should open an issue about this but I saw that you are using Solid’ createMutable which is not recommended and is intended mostly for easier transition from libraries with similar APIs. Other than not having read and write segregation it also leads to over subscription. Maybe you guys are aware of that already, just wanted to make sure.

[trusktr]

It is totally conceivable people can write all their state variables using createSignal (the fastest option), so outputting that would be totally fine. f.e.

const [foo, setFoo] = createSignal(...)
const [bar, setBar] = createSignal(...)
const [baz, setBaz] = createSignal(...)
// ...etc...

Maybe less ergonomic than stores in various cases, but still legitimate and still an idiomatic option

[steve8708]

Should we not just use signals? What’s the downside to the most simple/idiomatic approach used in solidjs’s docs? Everything else here sounds more complex and deviates from the idea of “generate code just like a developer would write” for a given framework

We should be able to just reuse all of our react hooks logic, just make sure all reads add a (), so not list but list() in the code, which is a normal sort of thing we do for other output types