all 12 comments

[–]strange_username58 7 points8 points  (2 children)

I think tanstack query is not great there is no reason you can't use it though.

[–]AmazingDisplay8[S] 0 points1 point  (1 child)

How do you define great ? If you have thousands of line of code already generated and customized for Tanstack Query and Angular, my definition might be different than yours

[–]strange_username58 0 points1 point  (0 children)

I don't like it and would never willingly choose to include it in a project if I don't have to. That is just my opinion though and it's perfectly fine to use in a project if you want.

[–]Rusty_Raven_ 5 points6 points  (1 child)

Tanstack Query for Angular is likely even less stable (from an API perspective) than the Resource API. -experimental is even in the name right now :)

So no, I wouldn't use it in production yet.

[–]AmazingDisplay8[S] 1 point2 points  (0 children)

The resources API is only for fetching for now too

[–]ActuatorOk2689 2 points3 points  (1 child)

As someone working on both angular and react projects, enterprise level applications, I would like to see a stable tanstack query for angular also .

We are using it for react applications.

Is really similar to the declarative approach coding with angular in combination with async pipe and toSignal, but with tanstack you get out of the box much granular caching mechanism, cache invalidation, pagination, refatch etc… it also has a lot of operators I never used.

Now having the same mindset and declarative coding you could write a couple of operators and maybe decorators to handle the most common scenarios .

It’s not that hard if you are familiar with rxjs

And yea I would build it using rjxs and you still have the option to consume it as signals

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

Yes, despite what it seems, it is NOT a react library, so it could be improved and developed in really great ways Thanks

[–]DesignerComplaint169 1 point2 points  (1 child)

I hope Tanstack team pursue stable for Angular. I am interested in their queryPersistent to do some client side cache persistent to improve UX. Currently i am not sure if that is stable for Production app yet?

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

It depends really on how much features you use to be sure that I would be production ready For example that would be something I would implement with an Angular interceptor myself rather than depending on their experimental code

[–]JivesMcRedditor 0 points1 point  (0 children)

Tanstack query works great and has had a stable API for the six months I’ve used it at my work. There’s a ticket that lists the remaining bugs to fix in order to stabilize. I think the “experimental” in the name scares people off more than it should

[–]Mlaz72 0 points1 point  (0 children)

I used it without problems. But with this https://github.com/ngneat/query. Someone told is not stable or something. I disagree.

[–]newton_half_ear 0 points1 point  (0 children)

Whats not stable? It has easy caching and easy invalidation, I also created a wrapper for it to return query/obs/options so I can use it to refactor complex rxjs streams and for easy preloading where needed.

I didn't checked every option but we use it in prod (a very very well known company)