React Flow | Svelte Flow - Powerful open source libraries for building node-based UIs with React (https://reactflow.dev) or Svelte (https://svelteflow.dev). Ready out-of-the-box and infinitely customizable.
0dbbe545 - pinch zoom on windows #37590dbbe545]:
b0b2d001 - re-observe when ref changesf452cf0c - fix redux readonly errorac2e11d1 - cover entire areaac2e11d1, b0b2d001, f452cf0c]:
d39d4269 - allow pinch zoom if preventScrolling=false685825c5 - set direction="ltr" for wrapper divd39d4269, 685825c5]:
This is hopefully the last release for React Flow 11. It fixes some bugs and adds a deprecation warning for node.parentNode which is now called node.parentId. There are two reasons for this: parentNode poses a name collision with the DOM API and it actually is an id not a node.
#4082 ba3809b1 - fix: re-observe nodes when hidden is toggled
#3935 6228d499 - disableKeyboardA11y now correctly prevents enter and escape key presses
Updated dependencies [c7a140bd, ba3809b1, 6228d499]:
b367173a - fix(subflow): show correct selection boxb367173a]:
59c44df5 Thanks @rhys-okane-instil! - fix internally used getNodeRect function814ae219 - fix getNodesBounds: use position instead of positionAbsolute for subflowsJust a tiny fix for Typescript users who want to use the new screenToFlowPosition and flowToScreenPosition function of useReactFlow.
e71dec26 - fix(react-flow-instance): add screenToFlow and flowToScreen typese71dec26]:
We want to make the migration for v12 as smooth as possible. That's why we added deprecation warnings for the following util functions:
useReactFlow.project to useReactFlow.screenToFlowPosition⚠️ changes: no need to subtract react flow bounds anymore!
before:
const reactFlowBounds = reactFlowWrapper.current.getBoundingClientRect();
const position = reactFlowInstance.project({
x: event.clientX - reactFlowBounds.left,
y: event.clientY - reactFlowBounds.top,
});
after:
const position = reactFlowInstance.screenToFlowPosition({
x: event.clientX,
y: event.clientY,
});
getTransformForBounds to getViewportForBounds⚠️ changes: returns { x: number, y: number, zoom: number } instead of [number, number, number].
before:
const [x, y, zoom] = getTransformForBounds(bounds, width, height, 0.5, 2)
after:
const {x, y, zoom} = getViewportForBounds(bounds, width, height, 0.5, 2)
getRectOfNodes to getNodesBoundsno changes, just a renaming.
useReactFlow.flowToScreenPosition
a114c75b Thanks - chore(utils): add renamed functions and deprecations, add useReactFlow.flowToScreenPosition
746fa4a0 Thanks @Nick-Lucas! - fix(intersection-helpers): use nodeRect instead of nodeOrRect291db12f - fix(panOnScroll): respect zoomActivationKeyPressed when hovering a nodee1d3d594 Thanks @juspy! - fix(useOnSelectionChange): multiple handlersddc40528 Thanks @bcakmakoglu! - refactor(pan-activation): allow panning by scroll when pan activation key is pressede4c25caf - refactor(handles): snap to handle center when above handlea114c75b, 746fa4a0, 291db12f, e1d3d594, ddc40528, e4c25caf]:
fix(panOnScroll): use correct filter so that connections work
Updated dependencies [e0cef7f1]: