You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-3Lines changed: 20 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,18 +8,35 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
8
8
9
9
This is a major release, and it might be not compatible with your current usage of our library. Please read about the necessary changes in the section about how to migrate.
10
10
11
+
### Added
12
+
13
+
-`<EdgeStraigh />`
14
+
- it's basically `<EdgeDefault />` without any special configs
15
+
-`<EdgeBezier />`
16
+
- only supported for v12, in v9 as straight edge is used
17
+
- use `curvature` property in the edge `data` object to define the bezier layout (0..1, default: 0.25)
18
+
-`<EdgeDefaultV12 />`
19
+
- the `data` object provides `markerAppearance` to set and remove the edge arrows
20
+
11
21
### Removed
12
22
13
23
- support for React Flow v10 was completely removed
14
24
15
25
### Fixed
16
26
17
27
-`<Modal />`:
18
-
- Add 'nopan', 'nowheel' and 'nodrag' classes to Modal's overlay classes in order to always prevent react-flow to react to drag and pan actions in modals.
28
+
- Add 'nopan', 'nowheel' and 'nodrag' classes to Modal's overlay classes in order to always prevent react-flow to react to drag and pan actions in modals.
29
+
30
+
### Changed
31
+
32
+
-`<EdgeDefault />` and `<EdgeStep />`
33
+
- support now v9 and v12 of react flow
19
34
20
35
### Deprecated
21
36
22
-
- support for React Flow v9 will be removed
37
+
- support for React Flow v9 will be removed in v26
38
+
-`<EdgeDefs />`
39
+
- use `<ReactFlowMarkers />` or build it on single `<ReactFlowMarker />`
23
40
24
41
## [24.4.0] - 2025-08-07
25
42
@@ -138,7 +155,7 @@ If you use Jest then you can use the same aliases for the `moduleNameMapper` con
138
155
139
156
### Migration from v24 to v25
140
157
141
-
- remove deprecated components, properties and imports from your project, if the info cannot be found here then it was already mentioned in **Deprecated** sections of the v24.* changelogs.
158
+
- remove deprecated components, properties and imports from your project, if the info cannot be found here then it was already mentioned in **Deprecated** sections of the v24.\* changelogs.
142
159
- we changed the integration of the supported react flow versions, formerly names `legacy` and `next` resources were renamed to more precise `v9` and `v10`, please see all info in the section about changes
0 commit comments