-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
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
docs(signals): add explanation of mutable change protection to FAQ #4679
docs(signals): add explanation of mutable change protection to FAQ #4679
Conversation
✅ Deploy Preview for ngrx-io ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea to add this to the FAQ 👍
Add a detailed explanation about freezing state and why it is necessary for Signals. Includes examples illustrating the issues caused by mutable changes and how to avoid them.
9c604a7
to
033fe07
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
I do wonder if we should wait to push this.
Yeah, let's maybe wait 😅 or just close it unmerged. |
@timdeschryver, the RFC is out #4683. I don't think that there is then any need for this PR. What's your opinion? |
@rainerhahnekamp lets close this PR and wait for the RFC result. |
Given the confusion around the need for immutable changes in Signals, it seems important to provide a more detailed explanation.
Adding this to the FAQ allows us to keep the main documentation concise and focused.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?