fabiospampinato
fabiospampinato
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
How could you possibly hope to control your updates if everything is always reactive?
~everything could possibly be reactive in Solid, where "everything" is basically either a function call or a property access, basically anything that could end up calling a function
31 replies
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
do you care about SSR/hydration?
31 replies
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
Examples: - switching between 2 virtualization modes on the same component, maybe one requires refs and the other doesn't, if you want to support that now you need to pass refs all the time, which for one of the modes is wasteful - maybe you have a createDebounced or something, supporting the wait time changing is trickier than it may seem (what happens if that's updated before it has a chance to trigger? do you reset the timer so the callback is potentially never triggered?). If you never need that there's no reason to even think about it imo
31 replies
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
even though there are some weird edge cases where for performance, or for simplicity, you do just want to say that something cannot be reactive because that's unsupported by your thing
31 replies
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
Like the use case you have is kinda thought to be non existent in Solid, you should support reacting to any prop
31 replies
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
Solid is meant to be used with the transform
31 replies
SSolidJS
Created by Fexelitche on 11/26/2024 in #support
Mass Normalization of Props
I think in general bailing out of the transform won't lead you to a pleasant path for Solid
31 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
worth checking now if a sibling memo is skipped too
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
It's better to try it with a sibling effect because the deeper effect could be under a root, under a separate owner, who knows
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
bug in Solid then I guess
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
that's very weird
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
the last 2 are on the same level in theory, I don't know why they are rendered like that
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
- some parent - some component - failing onMount - sibling memo
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
for suspense I guess maybe you can check if a sibling memo is instead always called
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
for the clenaup case you can check if a cleanup there is instead always called
130 replies
SSolidJS
Created by Katja (katywings) on 8/20/2024 in #support
onMount randomly not called
What comes to mind is that either it's getting disposed, or it's getting suspended, or something weird is happening like throwing inside a cleanup handler or something
130 replies