Popular posts

Mind = blown.... I did not know that. WOW!!! . But is there a solution to this is the component is a functional one? There is no way to put a shouldComponentUpdate or extend PureComponent in that.

As far as i know is the core of that Problem es6 classes. That whole function binding comes from es 6 class scope behavior and does not affect functional written components. I read an article from a react team member about that. I‘ll look if I can find it, I’ll post the link.

And since you want to use reacts synthetic events you have to use es6 classes.

The solution to this is basically bind function in the constructor or via arrow function in the class. The binding then is „stable“ because it lives as long the component lives.

Here is the react documentation about binding and the why.

reactjs.org/docs/handling-events.html

TLDR: in classes the functions are not Auto bound to the class which can cause „this“ to be undefined. Functional components which are pure functional auto bind it’s methods to the current context. That’s why it’s only a matter of class components.

I'll get back to later, I'll do some research... Thank you...