agentsmith
Reactivity with shadcn-solid textfield
I tried that originally, but I'll try again. Either way I'm about to just move on. It's mostly working. The app won't break because the value will be clamped even if the user can type in values outside of the min/max if they know how.
14 replies
Reactivity with shadcn-solid textfield
That looks like it should work.
I think it's a bug/restriction in the shadcn-solid component. It does work as expect if I use that and a regular input.
But the issue is still there if I use the shadcn-solid components.
14 replies
Reactivity with shadcn-solid textfield
I've identified the issue and it's a reactive thing, but I don't know how to fix it yet.
I can change the input value and when I do so it invokes the handle input which applies the clamp. This results in the underlying signal sticking to the value I expect. However, because the clamp results in the value being the same it doesn't trigger an update to re-render the input with the correct value.
This seems like a fairly common use-case when using inputs. Is there a way to deal with this in solid?
14 replies
solid-plotly.js a new wrapper for Plotly.js
Based on the error and the JS calls it looks like it's trying to insert an element in the DOM, but getting an error the the el reference is not present yet. The
el
is in JS at this point for sure, but maybe it's not rendered just yet.
It should be because it's in the onMount function, but the error is related to accessing an element that not yet loaded in the DOM.
This also explains why the await new Promise(resolve => setTimeout(resolve, 0))
resolves the issue becuase it needs just one more tick to be loaded.105 replies
solid-plotly.js a new wrapper for Plotly.js
The babel error is because of the size of plotly. It is a peer dependency for the library. It's the application that gives that warning when running because of the size of plotly, but there's not much to be done about that. It's just a large library.
105 replies