Moritz Klack

This is very good idea. I am thinking about moving the docs to docusaurus. What do you think about that?

Thanks for the input! The key handling is a hidden feature somehow ;) We really need to rework the docs.

I would add an option like { worldSrc : 'data/world-data.json' }. By default you could check a path like "data/world.json" like you described it in the readme

 There is a little button "Open in Codesandbox" in the bottom right corner that shows the whole code of that example: https://codesandbox.io/s/zbu68r?file=/App.js&from-sandpack=true. But you...

Hey @ncthbrt thanks for this detailed RFC! Even if React Flow wasn't built for huge graphs, I really like the idea of having a better support and a better performance...

That would be great, but let's wait for @peterkogo feedback here. I know he is also interested in the topic and maybe he already started something! Would you like to...

Thanks for the deep dive and the detailed explanation @peterkogo! We could fork rbush and publish it under @xyflow/rbush. If your PR mourner/rbush#138 gets merged, we can replace the dependency...

Currently we create a box of the connected nodes. We could do the same here and create a tree for the edges too. wdyt @peterkogo

That's not possible with the built-in functions. As you suggested @amirrezapanahi you can optimize this by using your own state management with your own `setNodes` / `setEdges` helpers.

could you try if it solves the issue if you memoize the `onChange` function with `useCallback`: ```js const UseOnSelectionChange: FC = (props: { setSelectedNodes: any }) => { const onChange...