You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @ngrx/* package(s) are the source of the bug?
signals
Minimal reproduction of the bug/regression with instructions
Using signalState, create a new store where the type of the value in the store is a class, and the value is set to an instance of that class. The documentation states that when the value in the store is an object, signals will be created for each property on the object (DeepSignal). But in the case where the object is a class instance, signals are not being created for each property, they are undefined.
If this isn't supported, that's one thing, but TypeScript still types each property on the value as a signal.
Hi @vtachkov, I haven’t found a solution yet. I’ve shared my PR with the experiments I’ve tried so far. If you or anyone else discovers a solution, your input would be greatly appreciated!
Which @ngrx/* package(s) are the source of the bug?
signals
Minimal reproduction of the bug/regression with instructions
Using signalState, create a new store where the type of the value in the store is a class, and the value is set to an instance of that class. The documentation states that when the value in the store is an object, signals will be created for each property on the object (DeepSignal). But in the case where the object is a class instance, signals are not being created for each property, they are undefined.
If this isn't supported, that's one thing, but TypeScript still types each property on the value as a signal.
Minimal reproduction: https://stackblitz.com/edit/typescript-dxfawb?file=index.ts
Expected behavior
Signals are created for each property on the signalStore value when the value is an instance of a class.
Versions of NgRx, Angular, Node, affected browser(s) and operating system(s)
NgRx: 18+
Other information
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: