Rainer Hahnekamp

@mfp22 An example could be that your component consumes an id property from the URL and needs to trigger a request for that particular entity. You use `input()` for property...

Yeah, let's get right to the bottom line: I would cover as much as I can with `effect` and use RxJs only where necessary. `rxMethod` is a perfect example. There...

I don't speak for NgRx. I am only here for the good discussions. > What happens if the id changes rapidly? If I deal with an event source that emits...

@danielkleebinder Here's the "open petition" to get it into the official repo: https://github.com/angular/angular/issues/56155 I'm sure Marko will not object ;)

Thanks, I never used it honstly. Was just a quick prototype. In our extensions we still depend on the non-public types. This feature would improve the situation, but only if...

@gabrielguerrero, I think - and please correct me if I'm wrong - we are talking here about two different features. - You need more feature functions and want to fix...

@Donnerstagnacht you find a working and typed solution at https://stackblitz.com/edit/ngrx-signal-store-starter-z3q5i5?file=src%2Fmain.ts Your `withIncrement` will not get the store but an wrapper function which patches the state. By doing that we can...

Hi @GuillaumeNury, yeah that's much better. In the end, it is the old story about getting access to the internal types, right?

@GuillaumeNury, @Donnerstagnacht: I've updated my version. Turned out that the only type we really need is `SignalState` and that one is public. So we can use the version of @GuillaumeNury...

There is no need for a separate `withFeatureFactory`. As described in https://ngrx.io/guide/signals/signal-store/custom-store-features#example-4-defining-computed-props-and-methods-as-input, the shown example can easily be solved with the existing functionalities: ```typescript interface Person { firstname: string; lastname:...