rowDirection warning
See original GitHub issueSince last update of react-sortable-tree v2.2.0, I have this new warning :
Warning: React does not recognize the
rowDirectionprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase
rowdirection instead. 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,
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:12
Top Results From Across the Web
Set RowRenderingMode from code. | Blazor Forums
I have a SfGrid which works fine. However, I'd like to set the RowRenderingMode from code something like: RowRenderingMode="@direction".
Read more >React Native: Scrollview won't scroll with row direction and ...
in my react-native app I have a scrollview where my list items are row wrapped (flexDirection:'row',flexWrap:'wrap'), however because of this my ...
Read more >Row class - widgets library - Flutter - Dart API docs
The row reports this by drawing a yellow and black striped warning box on the edge that is overflowing. If there is room...
Read more >Crop row direction can influence yields - Farm Progress
Higher demand for organically grown foods has farmers seeking new methods to increase crop yields and reduce weeds.
Read more >A Complete Guide to Flexbox | CSS-Tricks
So I used Flexbox to lay out the columns in left-to-right (row) direction, and then lay out each child in each row in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@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.
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: