Since last update of react-sortable-tree v2.2.0, I have this new warning :
Warning: React does not recognize therowDirectionprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercaserowdirectioninstead. If you accidentally passed it from a parent component, remove it from the DOM element.
I don't pass any rowDirection parameter on my instanciation ....
Can you check this ?
Thanks,
I have the same problem. Would be nice to get this resolved.
I am also seeing this console error. Here is the full stack trace:

Any update on this ?
I'm also seeing this error
yep.. ditto
I have the same problem
+the same problem
Try this :
const { test, test2, ...rest } = this.props
delete rest['rowdirection']
See #213. I solved #370 in exactly the same way as #213: by reading the current version of https://github.com/frontend-collective/react-sortable-tree/blob/master/src/tree-node.js and updating my code, namely:
class Node extends React.Component {
render() {
const { <a list of variables...>, rowDirection, ...restProps } = this.props;
<...>
}
<...>
}
Node.defaultProps = {
<...>,
rowDirection: 'ltr', // like in the original tree-node.js
};
Node.propTypes = {
<...>,
rowDirection: PropTypes.string,
};
@kbulygin Sorry can you explain how you fixed this problem. This seems more of a workaround then a proper fix.
I'm also not following the workaround you suggested. It looks like your adding the missing property and wrapping the original SortedTree Component created a new component.
Actually, the issue is caused by the theme which i'm using. https://github.com/frontend-collective/react-sortable-tree-theme-full-node-drag/issues/6
Looks like the proper fix never moved over
Most helpful comment
@kbulygin Sorry can you explain how you fixed this problem. This seems more of a workaround then a proper fix.
I'm also not following the workaround you suggested. It looks like your adding the missing property and wrapping the original SortedTree Component created a new component.