-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
(fix) - restore debounceRendering after act #1683
Conversation
…eact into fix/restoreDebounceRendering
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.
Super awesome 👍🎉 That's top notch code golf right here💯
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.
The code looks good to me. I'm just fighting an issue following a Node upgrade and then I'll test with the app/product tests where I ran into the original issue.
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.
Upon further testing it looks like this partly fixes the problem, but I'm afraid I found a second bug. If options.debounceRendering
was not set prior to setupRerender
being called, then options. __test__previousDebounce
is set to undefined
and the cleanup code in teardown
does not reset options.debounceRendering
.
A possible solution would be to test for the presence of the property in teardown
rather than it not being undefined
.
@robertknight it should be fixed now |
…eact into fix/restoreDebounceRendering
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.
That works. LGTM!
Fixes: #1681