until-destroy VS rx-angular

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.

RFC: @rx-angular/state/signals - extended signal and new eventEmitter

It has been a while now since the Angular team has been exploring (way more than we can think) alternative reactivity models and looking for something that lies between the extremes of naive Zone.js (i.e. Zone.js without OnPush) and Zoneless Angular combined with special pipes & directives like those provided by RxAngular.

I would recommend exploring https://github.com/rx-angular/rx-angular. Contributors did a huge research about using Angular to get the best results.

It also includes RxAngular, a toolset focused on runtime performance and template rendering, and taiga-ui, an UI component library.

There is another reason not to use async pipes. If you provide 'noop' zone, async pipes will stop working. In my experience it's better to start without zones if you know that performance might be a problem in the future. Working without zones has more benefits https://github.com/rx-angular/rx-angular/blob/main/docs/general/zone/why-zone-less.md Here is the list.

Another cool lib which goes into the same direction as NgRx Component Store: https://github.com/rx-angular/rx-angular/blob/master/libs/state/README.md

Here are some examples: https://github.com/rx-angular/rx-angular/blob/master/libs/state/docs/usage.md

We also added listings using the same pattern. This is the first time we used *rxLet. It really makes working with all Observable in the templates easier do check it out. It allows you four states for an observable suspense, error. complete so that you can handle each one of them separately and gets rid of the *ngIf with async pipe. Like if you want to display something else while loading and error is a big disadvantage of the async pipe when used with an api.