You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, in the source of connectAdvanced line 255 it seems there is a typo in the comment
//Doing it this way vs having a permanent componentDidMount that does
// a boolean check every time avoids an extra method call most of the time, resulting
// in some perf boost.
How to do a boolean check in the 'componentDidMount' for the succesive update since it will only be called once in the lifecycle? Could you explain how to use a permanent componentDidMount method that does the same thing like the current temporal 'componentDidUpdate' approach?
Thank you.
The text was updated successfully, but these errors were encountered:
Thank you. It makes sense now. I guess the logic here is that only when an update triggered by its onStateChange needs to do the notifyNestedSubs. If we implement a permanent componentDidUpdate then if it is triggered by a parent's re-render it should have a boolean to stop it from doing the notification.
Hi, in the source of connectAdvanced line 255 it seems there is a typo in the comment
//Doing it this way vs having a permanent
componentDidMount
that does// a boolean check every time avoids an extra method call most of the time, resulting
// in some perf boost.
How to do a boolean check in the 'componentDidMount' for the succesive update since it will only be called once in the lifecycle? Could you explain how to use a permanent
componentDidMount
method that does the same thing like the current temporal 'componentDidUpdate' approach?Thank you.
The text was updated successfully, but these errors were encountered: