Younes Jaaidi

I mistakenly created a duplicate here https://github.com/angular/angular/issues/46692 This could look something like this: ```ts interface LifecycleHooks { init$: Observable; changes$: Observable; destroy$: Observable; ... } ``` and could be implemented...

Hi @TheLarkInn, I just implemented this feature using a `keepUrl` option and here's the PR: https://github.com/TheLarkInn/angular2-template-loader/pull/39 But I'm still not satisfied with it's name :) any better ideas? Thanks!

Hi all 👋 What about adding a `sunset` field? The `sunset` field could indicate the next version where the deprecated item will be removed. It could look like this: ```yaml...

> Could you help me with a use-case? What is the benefit of having sunset (a runtime HTTP header that talks about removal) in OpenAPI specifically? > > You can...

> The private store pattern is only available with angular 14, right? So we would need to migrate, thus losing backward compatibility for older angular version. At least that's what...

Hi @mhamri, that's the reason why I separated Engine/ViewModel from State. They are the glue taking care of triggering change detection when necessary. Nothing more magic or implicit than native...

@BioPhoton as a follow-up to our conversation about RxSignals, I still didn't dive in depth in the PR but concerning the transformers typing issue, I think I've got something... except...

Thank you @edbzn for summarizing our discussion into this detailed issue! Good job! I usually call it `progressify` as it informs you of the progress state (pending, finalized etc...) even...

It would be interesting to add a progress merging operator that could be used like this: ```ts interface State { progress: Progress; } this.state.connect('cats', getCats().pipe(progressify())); this.state.connect('dogs', getDogs().pipe(progressify())); this.state.connect('progress', mergeProgress(this.state.select('cats'), this.state.select('dogs'));...

Hey! We just released `suspensify` in [`@jscutlery/operators`](https://www.npmjs.com/package/@jscutlery/operators) with @edbzn. We can incubate the operator there and collect feedback then migrate it to `@rx-angular/cdk`. What do you think?