Possible finddom node fix

[zackify]

No description provided.

[dphaener]

@zackify That looks like it should work. I'll want to definitely pull it down and test it before merging. If that isn't calculating the size on the proper element, it's going to cause all sorts of problems.

[zackify]

It's the same as doing a finddomnode on the component. A ref returns it's dom node. Just make sure tho!!

…

On Mon, Mar 20, 2017 at 16:41 Darin Haener ***@***.***> wrote: @zackify <https://github.com/zackify> That looks like it *should* work. I'll want to definitely pull it down and test it before merging. If that isn't calculating the size on the proper element, it's going to cause all sorts of problems. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAbacOs4_0v3ud4FBu3azySsCO8KoW6Qks5rnuR4gaJpZM4Mi-id> .

[dphaener]

@zackify Yeah but that cell is wrapped in a HOC, so......not 100% certain we will be referencing the same DOM node.

[gavmck]

String literal refs are depreciated now as far as I'm aware. Should be using the arrow function syntax instead.

Have submitted a pull request that addresses the same issue :)

https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/no-string-refs.md