-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
9.19 throws setState(...): You passed an undefined or null state object; instead, use forceUpdate() #1119
Comments
Can you provide a codesandbox with a repro? And perhaps a more detailed error message? |
OK, I'll have a look at making one. |
react 16 allows return https://teamtreehouse.com/library/returning-null-from-setstate. I would suggest upgrading react. but it's also just a warning in dev. I'll look into refactoring some Hope that helps! |
I've especially downgraded to React 15.6 until the Chrome translate bug is fixed in React 16. But I don't understand this already seems to be a breaking change, then why is it just a minor release? |
Its because there was no changes that weren't backwards compatible following semvar and the rewrite to 16.x lifecycle functions had no api changes. |
@TrySound Should this be a breaking changes? |
Yep this is a breaking change. Try to fix it. We will return null in v10. |
Gotcha |
Upgrading to 9.19 started throwing a React warning with React 15.6:
I'm using it like this:
The warning happens when scrollToIndex is updated.
The text was updated successfully, but these errors were encountered: