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
Stack Size Exceeded during shouldComponentUpdate #368
Conversation
Codecov Report
@@ Coverage Diff @@
## master #368 +/- ##
==========================================
+ Coverage 97.6% 97.61% +0.01%
==========================================
Files 3 3
Lines 292 294 +2
==========================================
+ Hits 285 287 +2
Misses 7 7
Continue to review full report at Codecov.
|
we encountered the same issue in one of our projects - waiting for this PR to be merged 👍 |
Is there intent to merge this? PR has been open for a while, if this won't be merged we'll consider forking or switching to |
@StevenLangbroek We were able to circumvent this issue by defining a
|
@laooola hey! while i appreciate that, we have a temporary fix in place. reason I ask is because we'd like to have some idea when we can retire what is essentially a hack around a bug. hope you understand. thanks ✌️ |
We have this issue with out project too when using Immutable.js, getting stack size exceeded errors with |
Fix in #402 |
Thank you for your PR! |
Similar to redux-form/redux-form#3461,
and as per mentioned reactjs/react.dev#7
I'm suggesting a safer deep equal comparison on the props to be generated.