Jovica Aleksic

yes, that for sure. But we'll go with class properties indeed, e.g. `handleChange = e => {}` - it's the lightest variant. I personally always use `autobind-decorator` in other projects,...

Alright, there's lots of instances across the codebase. Should take some time and go through them one by one. I totally agree that we shouldn't dynamically bind, as it creates...

Not currently. But PRs are welcome. Otherwise, I'll try when I find some time.

@bosgood I keep running into this error using your method: ``` Uncaught TypeError: Cannot read property 'on' of undefined at React3DInstance.objectMounted (React3Instance.js?02b4:881) at React3DInstance.objectMounted (React3Instance.js?02b4:905) at SceneDescriptor.setParent (THREEElementDescriptor.js?5394:308) at InternalComponent.createChild...

Still work in progress, but I ended up with this approach, successfully: ``` import React, { PureComponent } from 'react'; import { PropTypes, THREE, autobind } from '@/libs'; export default...

While I am not manually changing the userData, I think I run into a related problem in https://github.com/toxicFork/react-three-renderer/issues/57#issuecomment-333309313

> These errors occur when you have subdirectories of a `typeRoots` directory (in this case `node_modules/@types`) that do not contain `index.d.ts` files. I agree the error message is mysterious and...

The one with a dot is still there ;) grab it..!

Having the same issue. Proposed syntax should do fine. +1

I am facing the `undocumentIdentifier` vs 100% coverage issue too, it seems to be a tradeoff situation. The question is whether it's a bug or a missing feature. Of course...