Rainer Hahnekamp

@alex-okrushko, thanks for the update. We (@mikezks, @manfredsteyer) think the main requirement is to be able to prevent `patchState` from modifying a signalStore from the outside. That's what `signalStore({readonly: true})`...

I have pushed a draft PR at https://github.com/ngrx/platform/pull/4199

Can I join in this?

Okay, about testing without TestBed: I think the number of stores without DI, will be a minority. You will very likely have an `HttpClient` or a service depending on it...

Just one addition: I think we should also include some type testing. I find that important for advanced use cases.

Hi, you want to create a spy on `patchState` itself? I am afraid that will not work. `patchState` as standalone is very similar to `inject`, which we also cannot spy...

@jits it looks like you want to spy on the Store's method itself, right? The example you are referring to, is about a service which is used in the Store,...

@jits What do you think about that? https://github.com/ngrx/platform/issues/4256

@markostanimirovic I think the documentation is done. Can we proceed with the videos?

@samuelfernandez this is exactly what I am suggesting. You won't get away with a simple `Readonly`. It has to be nested as well. Here's the proposed type for that: https://github.com/markostanimirovic/ngrx-signal-store-playground/pull/2/files#diff-6230b858ba0b18996436aa5baa97a540a8e759a69f53b6880196d5fbf93e8f46