Conversation
☁️ Nx Cloud ReportWe didn't find any information for the current pull request with the commit 4e2a373. Check the Nx Cloud Github Integration documentation for more information. Sent with 💌 from NxCloud. |
| import { RxStrategyProvider } from '@rx-angular/cdk/render-strategies'; | ||
| import { Subject } from 'rxjs'; | ||
|
|
||
| @Directive({ selector: '[signalLet]', standalone: true }) |
There was a problem hiding this comment.
At this point, I'd just call it let directive as signals are going to be the recommended approach going forward
There was a problem hiding this comment.
I would reconsider the ideas in the template in general. The recent releases change a lot and we should adopt to the "modern way".
| } | ||
| } | ||
|
|
||
| function toObservable<T>(input: Signal<T>): Observable<T> { |
There was a problem hiding this comment.
Do we want to remove this in favor of Angular's toObservable?
| get<K extends keyof T>( | ||
| target: SignalStore<T>, | ||
| p: K | string | symbol | ||
| ): Signal<T[K]> { |
There was a problem hiding this comment.
Here we say Signal<T[K]> but in the initialValue we have signal(val ?? null)
Do we want to have it as Signal<T[K] | null> ?
Description
https://hackmd.io/gf5D1kC0RVKfDrJZXY-V0Q
State
Connect a signal
Computed from state
Signal from state
Effect from state
To be discussed
Template
To be discussed
transitionlike API (as in react concurrent mode) to have a scheduled signal usingRxRenderStrategiesinternally?