Skip to content

Rename strict effects / unsafe effects to use the reusable state terminology #4505

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

Merged
merged 1 commit into from
Mar 28, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/strict-mode.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ The legacy context API is error-prone, and will be removed in a future major ver
Read the [new context API documentation](/docs/context.html) to help migrate to the new version.


### Detecting unsafe effects {#detecting-unsafe-effects}
### Ensuring reusable state {#ensuring-reusable-state}

In the future, we’d like to add a feature that allows React to add and remove sections of the UI while preserving state. For example, when a user tabs away from a screen and back, React should be able to immediately show the previous screen. To do this, React support remounting trees using the same component state used before unmounting.

Expand Down Expand Up @@ -175,4 +175,4 @@ When the component unmounts, effects are destroyed as normal:
> This only applies to development mode, _production behavior is unchanged_.

For help supporting common issues, see:
- [How to Support Strict Effects](https://github.com/reactwg/react-18/discussions/18)
- [How to support Reusable State in Effects](https://github.com/reactwg/react-18/discussions/18)