Brendonovich
Brendonovich
Explore posts from servers
SSolidJS
Created by ⱼ ₒ ₑ on 1/17/2025 in #support
How to use server function & suspense
What's the problem you're having? The only wrong thing i can see is passing the ~/assets/img string directly into src
9 replies
SSolidJS
Created by quinnvaughn on 1/14/2025 in #support
useParams not updating with urql's createQuery
though that pr was closed so rip
19 replies
SSolidJS
Created by quinnvaughn on 1/14/2025 in #support
useParams not updating with urql's createQuery
19 replies
SSolidJS
Created by quinnvaughn on 1/14/2025 in #support
useParams not updating with urql's createQuery
Hmm it seems like the draft solid bindings for urql have a better implementation of createQuery that takes a function as an argument rather than a plain object
19 replies
SSolidJS
Created by quinnvaughn on 1/14/2025 in #support
useParams not updating with urql's createQuery
It's hard to say, I'm not sure if that urql lib handles reactivity properly
19 replies
SSolidJS
Created by quinnvaughn on 1/14/2025 in #support
useParams not updating with urql's createQuery
Also I’d get rid of that signal you’re setting into, accessing params is reactive
19 replies
SSolidJS
Created by quinnvaughn on 1/14/2025 in #support
useParams not updating with urql's createQuery
This will depend on how urql’s solid lib works, but you need to pass the value in a reactive manner, arm you’re just passing in the value at the time of execution. Try making the id field a getter
19 replies
SSolidJS
Created by gerard on 9/15/2024 in #support
crazy bug global store + solid router
I can provide a repro with tanstack router if that’d be helpful, but I haven’t figured out how to get a min repro yet
10 replies
SSolidJS
Created by Greenman999 on 12/30/2024 in #support
Error Boundary does not catch errors of the resource
oh lol even after it errors you can hit refetch and it can go back to the ready state, ui just doesn't show it
32 replies
SSolidJS
Created by Greenman999 on 12/30/2024 in #support
Error Boundary does not catch errors of the resource
yeah that checks out, the uncaught error breaks the ui's reactivity but the resource's internal state is still correct
32 replies
SSolidJS
Created by Greenman999 on 12/30/2024 in #support
Error Boundary does not catch errors of the resource
unless what you were saying only applies to the properties after reactivity has already been frozen, which does make sense
32 replies
SSolidJS
Created by Greenman999 on 12/30/2024 in #support
Error Boundary does not catch errors of the resource
so it seems that .state, ,loading, .error appear in the view in the state they were when the resource was read.
i don't think this is the case, they appear according to whatever the current value is, but when you do users() on its own i think any error will flow through to the root-level owner and essentially break all reactivity, stopping them from updating 😅
32 replies
SSolidJS
Created by gerard on 9/15/2024 in #support
crazy bug global store + solid router
@ryansolid would you be able to check this one out in january? i'm running into it once again porting tanstack router to solid, this time it's surfacing as accessing the value in a Show callback is throwing stale read errors, even though the when condition is valid, so the internal createMemo must be returning undefined
10 replies
SSolidJS
Created by Zikado on 12/18/2024 in #support
Different server context when using "use server"?
This is just a behaviour of start/vinxi at the moment, I think server functions and api routes use separate builds so they can’t really have shared state like that. There’s an issue open about it somewhere
5 replies
SSolidJS
Created by jack on 12/15/2024 in #support
dealing with data shared between pages
yeah fair, those are a bit more holistic
38 replies
SSolidJS
Created by jack on 12/15/2024 in #support
dealing with data shared between pages
i'd say that makes sense, they're router apis afer all, not start apis
38 replies
SSolidJS
Created by jack on 12/15/2024 in #support
dealing with data shared between pages
no the data is fetched by the route, but since props are read lazily the resource read happens in the component underneath its own suspense
38 replies