anthy Comments - Answer Overflow

anthy

•Created by anthy on 3/11/2025 in #support

resource.error works unexpectedly

Yeah, its not exactly how I use it like in the example, wanted just to show my point, the only issue I had was why was there nothing in the .error. I handle {test()} manually

9 replies

SSolidJS

•Created by anthy on 3/11/2025 in #support

resource.error works unexpectedly

Oh! That does it, thank you! :)

9 replies

SSolidJS

•Created by anthy on 3/11/2025 in #support

resource.error works unexpectedly

In my use case I would rather avoid using the error boundary because my layout looks something like this:

  <div>Lots of information {test()}</div>
  <div>{test.error.message}</div>
  <div>Lots of information {test()}</div>

  <div>Lots of information {test()}</div>
  <div>{test.error.message}</div>
  <div>Lots of information {test()}</div>

I want those two divs to be always rendered. If I were to wrap that component in an error boundary it would replace it alltogether

9 replies

SSolidJS

•Created by anthy on 3/11/2025 in #support

resource.error works unexpectedly

whats the point of the .error field if im supposed to use the ErrorBoundary

9 replies

SSolidJS

•Created by anthy on 2/20/2025 in #support

"Simulating" loading state with createAsync

Also isn't .latest to be removed?

6 replies

SSolidJS

•Created by anthy on 2/20/2025 in #support

"Simulating" loading state with createAsync

From within the table you can change params which will retrigger the query. And then I want the stale data in the table and the spinner on top

6 replies

SSolidJS

•Created by anthy on 2/14/2025 in #support

Initial search params

In the worst case scenario I could modify your suggestion to do what I want now that I think about it. I could probably create a separate signal something like areParamsReady and guard against that. Doesn't seem like the cleanest solution in the world tho heh

6 replies

SSolidJS

•Created by anthy on 2/14/2025 in #support

Initial search params

It's not really what my problem is though, the empty params will be correct too. What I want is if there are default ones present I want them to be loaded into the router before the createAsync runs

6 replies

SSolidJS

•Created by anthy on 2/14/2025 in #support

Initial search params

Its gives feedback to the user that their default params were applied

6 replies

SSolidJS

•Created by hcker2000 on 10/11/2024 in #support

Importing bootstraps JS

can you share some code? Also wdym by functions?

8 replies

SSolidJS

•Created by anthy on 10/10/2024 in #support

Input type="reset" clears out wrapped inputs

Manually using attr:value helped, thanks!

8 replies

SSolidJS

•Created by anthy on 10/10/2024 in #support

Input type="reset" clears out wrapped inputs

Oh yeah, and the question is is this a bug and if not is there a workaround?

8 replies

SSolidJS

•Created by anthy on 9/9/2024 in #support

Retrigger fetcher in createResource on store change

() => { ...store } works too lol

6 replies

SSolidJS

•Created by anthy on 9/9/2024 in #support

Retrigger fetcher in createResource on store change

JSON.stringify works but that trackstore thing doesnt 😦

6 replies

SSolidJS

•Created by anthy on 9/9/2024 in #support

Retrigger fetcher in createResource on store change

For the context I'm simulating query params as an in memory Solid store and want to refetch data on their change. Thats why I'd like to pass the store as the signal. Conveniently it also becomes the fetcher argument

6 replies

SSolidJS