remove the need for `props.attributes`

This is one of the most awkward things when defining custom Node components. Right now you have to remember to mix in <Component {...props.attributes} /> to your components, because some things depend on it…

• findDOMNode depends on an attributes.data-key property being set.
• Right-to-left text direction depends on an attributes.dir property being set.

But why not solve this with React’s refs instead? In the core <Node> component, when the ref is established it could just use ReactDOM.findDOMNode itself and set those two properties on the node’s element?

This prevents the user from specifying exactly which element to mix the attributes in on, but I’m not sure that’s even a thing we want to allow…

Feels like this would be a super simple, but nice API improvement. If anyone sees holes in the plan please point them out!

[AlbertHilb]

@ianstormtaylor It would be beautiful to remove props.attributes, but we should avoid overusing ReactDOM.findDOMNode. findDOMNode is considered an anti-pattern and could be removed in a future React release. See this discussion for example.

[twobit]

Downshift takes a similar approach to mixing in library controlled props with prop getters. Also check out the blog post with more details.