Expose Solid Query setStore in setQueryData

[14gasher]

Solid allows us to do fine grained updates with stores. Under the hood, solid query is using stores to store information.

Optimistic updates would be incredibly powerful were we able to do fine grained updates with the set store functionality. This would help prevent unnecessary changes from happening and add a whole new layer of reactivity to an already impressive library.

Just my 2 cents haha.

[PeterDraex]

I'm also interested in this. Currently, as setStore is not exposed, it's impossible to do an optimistic update without re-rendering the while resultset. If I have a list with 1000 items and I modify one property of one item, all 1000 items will get all their components re-rendered from scratch. There is no way to avoid this, right?