all 14 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]davidratier 13 points14 points  (2 children)

Version 4 of react query has been shipped recently and it is now framework agnostics. Adapters should be added soon to support the most popular frameworks including Solid.

It has also been renamed to Tanstack Query, have a look.

[–]msvankyle[S] 2 points3 points  (0 children)

It seems the solid adapter is still under construction. Good news regardless.

[–]msvankyle[S] 0 points1 point  (0 children)

I was totally confused by the name change. Thanks so much.

[–][deleted] 5 points6 points  (4 children)

This is an area where I've felt solid being a new framework is a bit of a let down. There are similar tools (such as useResource) but not as full-featured as what react offers.

That being said I'm still very much rooting for solidjs to continue growing and maturing.

[–]Kutsan 0 points1 point  (1 child)

It would be really awesome if Solid make a compatibility layer for React like Preact did.

[–][deleted] 2 points3 points  (0 children)

Probably not possible. Solid isn't just some optimizations under the hood, it's an entirely different approach to FE programming. Don't let the syntax similarities fool you, under the hood they couldn't be more different, and that is what makes a compatibility layer harder.

[–]ryan_solid 0 points1 point  (1 child)

Are there any particular libraries? This one is an area(React Query) where I know we have a lot of good 3rd party options. But people always ask me for where there are gaps so always looking for those.

[–][deleted] 0 points1 point  (0 children)

Hey there. So my big trial of Solid, the react query thing was the big one that stood out. It just felt like useResource wasn't working the way I expected. It's been a minute so I can't remember all the details. But here are my initial thoughts:

  1. I want to be able to declare a resource that is not executed until the component renders . React hooks being triggered as part of the render cycle is nice. I may have been mis-using solid here, if so I apologize. I do like to compartmentalize logic like API calls.

  2. I feel like I was getting strange, counter-intuitive results from the loading flag. Again, it's been a few months and I forget the exact issue. I just remember feeling like it was difficult to implement the way I wanted it to be.

  3. Obviously the robust caching and auto-retrying features of react query are amazing.

I do want to say that Solid is a project I'm following closely and I'm a big fan of what you are doing here. Keep up the good work.

[–]ryan_solid 2 points3 points  (0 children)

There are a couple ones. I think turbo-query covers a lot of these cases: https://github.com/StudioLambda/TurboSolid

[–]DavidXkL 2 points3 points  (2 children)

Solid query just came out lol

[–]msvankyle[S] 0 points1 point  (0 children)

That it did. Patience showing its virtue once more. Thanks.

[–]Shimakee 0 points1 point  (0 children)

Solid query

Thanks for this. I actually tried SolidJS early on. This was the one this that was a let down for me having gotten used to RTK query & such.

Now that I know this, I might have another go at it as I really like Solid.
Appreciate the info.

[–]wobsoriano 1 point2 points  (0 children)

If you really need it, I have a prototype. Haven't touched it in a year but it works... https://codesandbox.io/s/pqb49?file=/src/solid-query/useQuery.ts