-
Notifications
You must be signed in to change notification settings - Fork 50
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
Consider forcing remount with some heuristics #15
Labels
Comments
This would be a very comfortable feature indeed. Can I help you with this somehow @gaearon? |
Yeah, feel free to experiment. You'd need to modify the code to create a new proxy class and prototype under some conditions and return them from |
any update here? @Yomguithereal |
Related to #39. Better to consider things Comprehensively. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If constructor,
componentWillMount
, orcomponentDidMount
code changed, we should probably force remounting. We can usetoString()
to check (it won't work for classic components though, as their method implementations are inside React itself so that they work with mixins).The text was updated successfully, but these errors were encountered: