Releases: pierpo/react-archer
Releases Β· pierpo/react-archer
Release v4.4.0
Release v4.3.0
Features
- You can now add a CSS class to the SVG paths! #194 Many thanks to @mikedidomizio π
Release 4.2.3
Features
- Expose
ArcherContainerRef
type for TypeScript. You may now use the ArcherContainer ref properly with TypeScript.
const archerRef = useRef<ArcherContainerRef>(null)
return (
<ArcherContainer ref={archerRef}>{children}</ArcherContainer>
)
Release 4.2.2
Bugfixes
- Fixes a warning with SSR rendering #186
Release 4.2.1
Bugfixes
- Fixes server-side rendering not showing arrows #184
Release 4.2.0
This release includes improvements in the code regarding the elements registration. It will fix bugs regarding this.
Please try this release if you had non refreshing elements issues π
Bugfixes
- No issues to link here, but some refreshing/registration bugs are fixed by the refactorings that this release includes.
Release 4.1.0
Bugfixes
-
Fixes a long-standing issue #38
- we now encode the arrow IDs so that they can be any string (no more restrictions with alphanumeric characters)
- we don't use the whole URL to display the arrow marker.
β οΈ This breaks on some older Safari versions, but this will solve an issue for all browsers when your app has#
in the URL.
-
If we fail to draw an arrow, we don't draw it to
(0, 0)
anymore. We simply don't draw it.
Release 4.0.1
Bugfixes
- Fixes compatibility with React 18 #172
Release 4.0.0
Breaking changes
- Dropped support of flow types. You may open a PR if you want to implement it with the new Typescript codebase (it's been dropped because the library was migrated from flow to typescript).
Changes
No new features. This is a technical upgrade, no added functionnalities.
What has been done:
- migration to typescript
- migration to react hooks instead of class components
- lots of refactoring. Components were split up, lots of renaming and extracted methods for the sake of clarity. Some tests have been made more robust, too.
This will make contributions easier π
It might solve some bugs accidentally. It might also introduce new ones, do not hesitate to create issues if it does!
No rewriting of the drawing logic has been made, though. The library still has the same limitations of v3. Working on it will be easier starting from today, though π
Bugfixes
- Fix a typing problem with React 18 using typescript