im_ninooo
im_ninooo
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
I can just use a <Show when={props.state === 'errored'}>, that's fine
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
I thought it was because the resource wasn't being called within it (inside the component) but it's still doesn't seem to work
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
the ErrorBoundary here doesn't seem to work..
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
I'll close this again, thanks again to both Tommy and REEEEE!
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
if it does, that's significantly cleaner! thank you so much 🙂
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
that's what I expected to see based on the truth table in the docs.
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
thanks for the suggestions 🙂
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
..I'll have to read on those again 😅
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
I really need to rewrite that.
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
I'll update and try again. I did change my loggedIn signal to be optional and defaulted to undefined meaning the session check hasn't run/finished and that worked but again, hooking solely on the resource's state would be cleaner 🙂
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
this is obviously not a big deal but I would like to show the correct information (or nothing at all). I know this should be possible by hooking into the checkingLogin signal, but that will make my code unnecessarily more complex.
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
my issue is that when the state is ready and the resource is undefined, I show a "No data available" fallback, but because that's also the initial resource state, that message is shown before the fetch begins (and then a "loading" message takes over).
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
unless an undefined value is considered resolved, which to me doesn't make sense (since it is undefined).
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
also, in which case would the state be unresolved? it seems like it would be for such cases
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
yeah, maybe but it would be nice if I could simply use the resource's state in my logic
49 replies
SSolidJS
Created by im_ninooo on 6/28/2023 in #support
Await for signal state?
(I'm on version 1.6.5 btw so maybe that already got fixed)
49 replies