until-destroy VS rx-query

Nice! I didn't know about this. I was using the `untilDestroyed` operator from this package, which does exactly the same thing: https://github.com/ngneat/until-destroy

Very cool. I’ve always used this library to deal with it in the past: https://github.com/ngneat/until-destroy

You can find the code of the UntilDestroy decorator by this link. All it does is patches the component's ngOnDestroy with unsubscription logic and call the original method at the end.

Hello angular community, I saw in some posts talking about custom decorators to manage subscriptions with components/ services I'm thinking about implementing our own custom decorator or use this package:https://github.com/ngneat/until-destroy

Btw, you should look at https://github.com/ngneat/until-destroy

https://github.com/ngneat/until-destroy may be helpful?

Akita is maintained by Datorama, they do a lot of great work surrounding Angular. Netanel Basal is part of that group, check him out on Medium.

If anyone knows about another angular package that provides caching and request status flags out of the box, please let me know (rx-query is unmaintained, other packages provide the loading spinner only)

Looks like rx-query was inspired by react-query but it's no longer maintained

Heard about https://github.com/timdeschryver/rx-query but never tried it. Looks like its not maintained anymore :(

I'm a little confused. How's this different from rx-query? (your own library) https://github.com/timdeschryver/rx-query

This is largely to set a precondition that you should avoid trying to use NgRx in situations where the API is handling all or most of the state for the frontend. If your UI only needs to know about the { data, error, loading } states of API calls for the most part (like when using Apollo or rx-query), then chances are NgRx isn’t a great option.