strblr

@nstadigs Interesting. How do you handle dragging the sub nodes automatically when dragging a parent?

Nice, do you do that just before `applyNodeChanges` or somehow in the event listeners?

Not really, given your description it should work. Each node has two invisible handles under the visible dot, just a bit wider. With a connection radius that goes even further....

I need the source handle to be larger than the node because when starting a connection, I want to be able to start from the edge (the node itself is...

I didn't manage to do it, so I simply didn't upgrade. It works well in all versions prior to 11.7.3, not sure why it broke.

Yes I could prefix it but it would end up quite messy. In my opinion it would make more sense that react-flow takes care of isolation on a per-context basis....

Thank you for your quick response @n1ru4l, I'm glad if my feedback was useful ! If I understand your idea correctly, it would be to pass the initial `contextValue` to...

@n1ru4l This would make `run` async, thus changing a lot of typings, and maybe it will have other side-effects that I'm not aware off. Is this really a no-brainer?

I tried to find a workaround without changing the library. I don't understand why something like this doesn't work: ```ts import { execute as defaultExecute, ExecutionArgs } from "graphql"; import...

Fixed it. There were two issues: - Composition order: `makeLazyContextExecute` needs to be wrapped inside `live.makeExecute` for it to be cached for invalidation, not the other way around. - Distinguishing...