Lukas Bach

Sorry, but I'm not completely sure what the problem is. In the render method of the item, one of the props should be a `startRenamingItem` method that you should be...

To avoid bubbling up click events from the context menu to the item renderer, I would first try to call `e.stopPropagation()` directly in the handler of the click events on...

Hi, thanks for reporting! Just as an heads up, I've looked into it, and it is not quite as trivial to fix; since checking whether someone is dropping an item...

Hi @C7X! When working with lists with thousands of entries, list virtualization starts to become inevitable. This is something I want to support with react-complex-tree in the future, but there...

Do you have an example repo where this can be reproduced? There is an example with a large (mostly flat) tree where drag-and-drop always has the correct drop location for...

Hi @AssisrMatheus, thanks for your contribution! Can you please explain which issue you are facing? The prop `hasChildren` denotes whether an item should behave like a container that has children,...

Hi @dlech, thank you so much for your contributions, I really appreciate them and your effort! I will look into them later this week and make sure to make them...

Hm I thought about your suggestion, but at the moment you can also pretty much write custom keyboard handlers by just listening to keydown events yourself and use an imperative...

> there is no access to the internal state of each item to know when an item should respond to a key event or not You should be able to...

As @madhums mentioned in the discussion, it would be helpful to see a codesandbox as an example of the specific issue, or some other details what makes the element wrong...