We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signals
Currently signal state is a strong utility to handle state even outside signal store. The missing part is allowing that state to be a linked signal.
I propose a new linkedSignalState which will allow deriving the state based on another signal.
linkedSignalState
This will allow resetting the state on signal change - or any other state transformation based on some other signal change.
Currently either don't use signal state or use an effect to update the state.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Which @ngrx/* package(s) are relevant/related to the feature request?
signals
Information
Currently signal state is a strong utility to handle state even outside signal store.
The missing part is allowing that state to be a linked signal.
I propose a new
linkedSignalState
which will allow deriving the state based on another signal.This will allow resetting the state on signal change - or any other state transformation based on some other signal change.
Describe any alternatives/workarounds you're currently using
Currently either don't use signal state or use an effect to update the state.
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: