Lukas Bach

Hi @downright-development! This is by design, the top-level items rendered by the tree are the children of what is defined as root item. This allows you to render several top-level...

The code base is currently still on React 18, but afaik there are no incompatibilities with React 19.

@wdcryer's PR is merged and deployed, thanks again for the contribution! I'll close this for now, please reopen if issues with React 19 persist.

Have a look at the default implementation of `renderItem`: https://github.com/lukasbach/react-complex-tree/blob/main/packages/core/src/renderers/createDefaultRenderers.tsx#L89 If an item is being renamed, the item is rendered as a div. Otherwise, it is rendered as button by...

Thanks for pointing that out @alzeebum, yes that is in fact not explicitly mentioned in the docs. If you would like to contribute that part to the docs yourself, feel...

@ck-cklinger I btw. noticed another issue in the code you posted in your initial post, though I guess you figured that out by now: ```typescript new StaticTreeDataProvider(items, (item, data) =>...

Hi, thanks for the report! I can't seem to access the codesandbox, and get a "Devbox not found" error. Can you please see if that sandbox has public access enabled?

Hi, sorry for remaining silent on this. I saw the sandbox and can reproduce the issue, but haven't had time to dig deeper, I'll update you soon on this again.

I guess the cause for the issue is, that by supplying a custom `ref` to your tree element, you override the ref supplied by the `treeItem.getProps()`, so some functionality gets...

Happy that this was helpful! I found that the follow up bug I mentioned, was not from calling `item.getProps()` twice, but rather that `item.getProps()` may not be called inside a...