react-arborist Version 4

Experimenting with what the next iteration of the react-arborist api will be, while maintaining all backward compatibility.

Remaining Items

[x] node.state
[x] require props hook
[x] disable drop function
[x] sort nodes
[x] filter nodes
[x] customizable commands object
[x] fix weird cursor positions
[x] outside drop
[ ] compatibility layer with <Tree /> props
[x] Make it with with no props
[ ] provide way to disable features
[x] RTL support
[ ] Variable height rows
[x] Scrolling callbacks
[x] Open all folders when filtering
[x] Open folder when dropping into it
[x] Open folder when hovering over it for a time
[ ] Custom Renderers
[ ] Two Tree Demo
[ ] Checkbox Demo
[ ] Everything is a folder Demo
[ ] Drag Handle
[ ] Duplicate Nodes
[ ] Trag between trees
[ ] Checkbox Demo
[ ] All Internal Demo
[ ] RTL Demo
[ ] Different Drag Previews
[ ] selectionFollowsFocus Demo
[ ] Use Single Selection

Mar 13 '24 22:03 jameskerr

@jameskerr

That's great and thanks for new version with great changes

Do you have a plan to put RTL support in this version

Mar 20 '24 07:03 mohsenomidi

@mohsenomidi yes, the next version will support RTL.

Mar 21 '24 18:03 jameskerr

Dear @jameskerr

Thanks for this PR.

We are exciting to have the features in i this PR, do you have any plans to merge the changes

🙏

Jun 28 '24 10:06 mohsenomidi

I'd be interested about your current status, any blockers still open?

Aug 04 '24 07:08 CHE1RON

Hello @jameskerr thanks for the update in https://github.com/brimdata/react-arborist/issues/275.

I had a few thoughts on finishing version 4, you have already done a LOT of work on the new version. Would that be enough to constitute a v4 release? The drop cancel issue I see you fixed as well (we fixed this recently ourselves also).

What else would you want for a v4 or if this is enough would it just be migration that needs to be written?

// Ben

Dec 03 '24 15:12 ben-hearn-sb

@ben-hearn-sb I do need some sort of migration guide. I would also like a compatibility component so it doesn't completely break if people upgrade.

For example, the <Tree/ > component is what is used in v3.

I removed <Tree /> in favor of <TreeView /> component is the upgraded component for v4.

I would like to add <Tree /> back to v4, make all the props compatible with v3, but in the body of the component just re-write the props and give them to <TreeView />.

If you'd be interested in helping write that I would welcome it!

Dec 03 '24 21:12 jameskerr

@jameskerr since we need the tree for the project we are building with it anyway, myself and my colleague have agreed that we should probably chip in and help maintain this :) Let us get our project rolling a bit more intensely first though, we are at a pivotal stage atm.

I didn't quite follow "I removed in favor of component is the upgraded component for v4." what this meant though?

Dec 23 '24 12:12 ben-hearn-sb

Very cool! Thank you.

Jan 16 '25 18:01 jameskerr

Hi, how is the update going? Can I help with anything? =)