jairajjangle / react-native-tree-multi-select Goto Github PK

const handleSelectionChange = _checkedIds => {
    // const slug = _checkedIds;
    console.log('slug:', _checkedIds);
  };

how to get data _checkedIds, i can't using setState for set value _checkedId, i need list value using to call api

It is really useful and most update.

I have very small enhancement request. If you accept name and children from props. It could be easy for us to pass any kind of data in our own structure.

it will reduce conversion to name and children.

Is your feature request related to a problem? Please describe.
I'd like to be able to create a reorderable tree view. Moving items with drag-and-drop gestures is more intuitive for the end user than, say, using a context menu

Describe the solution you'd like
new props that can be passed to the TreeView component:

• canDragNodes: boolean
• onDragFinished: (oldIndex: number, newIndex: number, draggedItem: TreeNode) => void

Describe alternatives you've considered
N/A

Screenshots or screen records
N/A

Additional context
There is an implementation of a draggable flashlist here that i think could be integrated

Would you like to work on this feature?
If you wouldn't mind adding another dependency, then sure :)

Is your feature request related to a problem? Please describe.
First of all, thanks for this truly amazing library!

My problem is that I need to use two trees in one view with different data sets, and since the library is using Zustand with a global store, both trees were showing the same set of values. I was able to overcome it with a dirty hack, but it would be great if there was the ability to use multiple trees in one view.

Describe the solution you'd like
The best solution would be to be able to have any amount of TreeViewes hosted on the same page with no data duplication. Something like:

<TreeView data={data1} />  
<TreeView data={data2} />

showing different data.

Describe alternatives you've considered
I ended up duplicating the store and duplicating the TreeView component (to have "TreeView2") for now, but it's a very dirty solution, it would be great if the library supported it.

Screenshots or screen records
NA

Additional context
NA

Would you like to work on this feature?
Unfortunately, I'm not good enough with React to be able to work on it

Is your feature request related to a problem? Please describe.
I was getting weird behavior, checking sort-of working but unable to un-check, when there were empty arrays of children, if I recursively delete any empty arrays of "children" attributes it works as intended, the library should gracefully handle an empty array.

Describe the solution you'd like
The library should handle no "children" attribute just as well / the same as an empty array children.

Describe alternatives you've considered
I had to add this to my function:

// Step 3: Remove empty children arrays
function removeEmptyChildren(rmArr: any[]) {
  rmArr.forEach(rm => {
      if (rm.children.length === 0) {
          delete rm.children;
      } else {
          removeEmptyChildren(rm.children);
      }
  });
}

removeEmptyChildren(tree);

Screenshots or screen records
NA

Additional context
NA

Would you like to work on this feature?
Potentially, havn't really dug into the code yet.

Hey!
Thanks for this incredible library!

Is there an approach for getting the count of checked subNodes under a node?

For example

└── Cars (2 out of 3)/
    ├── [x] Hyundai
    ├── [x] Benz
    └── [ ] Tesla

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Updating multiple npm lock files is deprecated and support will be removed in future versions.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency react-native-builder-bob to ^0.23.0
• fix(deps): update dependency org.jetbrains.kotlin:kotlin-bom to v1.9.24
• fix(deps): update flipper_version to v0.250.0 (com.facebook.flipper:flipper-network-plugin, com.facebook.flipper:flipper)
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/config-conventional, commitlint)
• chore(deps): update dependency @release-it/conventional-changelog to v8
• chore(deps): update dependency @types/react to v18
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-config-prettier to v9
• chore(deps): update dependency eslint-plugin-prettier to v5
• chore(deps): update dependency gradle to v8
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency release-it to v17
• chore(deps): update dependency semantic-release to v24
• chore(deps): update dependency turbo to v2
• fix(deps): update dependency @gorhom/showcase-template to v3
• fix(deps): update dependency org.jetbrains.kotlin:kotlin-bom to v2
• fix(deps): update dependency react-native-vector-icons to v10
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @evilmartians/lefthook to v1.6.15
• chore(deps): update dependency @semantic-release/github to v10.0.6
• chore(deps): update dependency @testing-library/react-native to v12.5.1
• chore(deps): update dependency ts-jest to v29.1.4
• chore(deps): update dependency turbo to v1.13.4
• chore(deps): update dependency pod-install to ^0.2.0
• chore(deps): update dependency react-native to v0.74.2 (react-native, @types/react-native)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Is your feature request related to a problem? Please describe.
I tried changing an existing data type in my project to extend TreeNode. However, since the ID is assumed to be a string, typescript complains.

Describe the solution you'd like
Change the TreeNode interface to be generic

export interface TreeNode<T> {
  id: T,
  // ...
}

Describe alternatives you've considered
N/A

Screenshots or screen records
N/A

Additional context
N/A

Would you like to work on this feature?
Absolutely!

Hi,

well done! Your control looks great, but is it possible to adapt your solution to single node selection? I need something exactly like this, but instead of checkboxes, for example, a radiobutton, where you can select only one node.

Thanks in advance for your answer!