Create signal from store element

I have a component that takes signal as a prop:

const NumberInput:Component<{value:Signal<number>}> = props => {
  // Stuff...
  return <input>{some fancy business}</input>
}

const NumberInput:Component<{value:Signal<number>}> = props => {
  // Stuff...
  return <input>{some fancy business}</input>
}

Elsewhere I have a store that contains an array of numbers:

const [store, setStore] = createStore([1,2,3]);

const [store, setStore] = createStore([1,2,3]);

My understanding is that SolidJS creates a signal for properties of stores. Is there a way to access that underlying signal so I can pass it to the input? I.e.

<NumberInput value={store[0]/>

<NumberInput value={store[0]/>

thetarnav•2/24/24, 9:16 PM

There is not
Typically you’d just call

GhirigoroOP•2/24/24, 9:18 PM

Not sure I understand. That sounds like a change to the implementation of the input. Elsewhere I do use signals for it so I still want to keep that interface

thetarnav•2/24/24, 9:20 PM

Either you don’t want to use stores
or that’s a bad interface
or you need some helper function

thetarnav•2/24/24, 9:22 PM

solid is designed against binding signals to components

thetarnav•2/24/24, 9:22 PM

so things won’t usually “implement Signal interface” so that could be bound this way

GhirigoroOP•2/24/24, 9:23 PM

OK. So if you have a component that is designed to both read and write to a value you shouldn't give it a signal prop? You should give it a value and a setter function?

thetarnav•2/24/24, 9:24 PM

well how do you do this with a regular ?

thetarnav•2/24/24, 9:24 PM

you have value prop and onInput callback

GhirigoroOP•2/24/24, 9:25 PM

Sure, but html doesn't have signals - primitives for setting and reading a value

thetarnav•2/24/24, 9:25 PM

that’s still the usual pattern

thetarnav•2/24/24, 9:26 PM

so you can go from native input to a component easily

GhirigoroOP•2/24/24, 9:28 PM

OK. Is there somewhere I can read up on this design. It strikes me as running counter to the tool (I'm sure it's not - I'm just inexperienced with Solid) so I'd like to understand why

GhirigoroOP•2/24/24, 9:28 PM

Is the idea to maintain similarity with HTML?

thetarnav•2/24/24, 9:35 PM

That’s one reason for sure, but there are two more I think

solid doesn’t want “a Signal interface” but just have a function for the source
it could be reactive, it could be a memo or could be just a regular function
same with setters I guess
to enforce a unidirectional data flow, where the children do not write to a signal directly, but rather it happens through explicit setters that can be tracked - it’s easier to see who can write to what and who can only read
at least in theory
For the resources I think I need to find a better person to give some

GhirigoroOP•2/24/24, 9:37 PM

OK. Thanks for the explanation. It's appreciated.

thetarnav•2/24/24, 9:42 PM

I’ve asked here maybe someone finds something .

https://discord.com/channels/722131463138705510/861229287868858379/1211065322321354772

GhirigoroOP•2/24/24, 10:04 PM

Thanks! I'll take a look