-
Notifications
You must be signed in to change notification settings - Fork 50.6k
Current behavior for Effect behavior in StrictMode when reordering #29595
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
4485e6b to
3b1f29b
Compare
|
Comparing: ea6e059...f94b10f Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show
|
3b1f29b to
f94b10f
Compare
| "passive destroy second: 1", | ||
| "passive create second: 1", |
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.
Just double invoking the second one.
| } | ||
| }); | ||
|
|
||
| it('effect invovation after key swap', async () => { |
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.
typo - invovation -> invocation
|
Do we want to rephrase the PR title? To |
Summary
Test for current behavior experienced in #29585.
How did you test this change?
yarn test --watch packages/react-reconciler/src/__tests__/StrictEffectsMode-test.js -t "effect invovation after key swap"