Skip to content

Commit

Permalink
chore(doc): improved change log documentation for M/L/C error
Browse files Browse the repository at this point in the history
  • Loading branch information
yisibl committed Nov 15, 2023
1 parent cfca7ad commit fa81b20
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,12 +127,12 @@ Eventually, we upgraded resvg for 2 successive versions, and are now at the late

- fix: 'the previous segment must be M/L/C' error. [#204](https://github.com/yisibl/resvg-js/issues/204) Thanks to @yisibl

This is a normal error thrown by resvg when parsing Path Command, and has been confirmed as fixed in resvg 0.29.0.
This is a normal error thrown by resvg when parsing Path Command and has been confirmed as fixed in [resvg 0.30.0](https://github.com/RazrFalcon/resvg/blob/master/CHANGELOG.md#fixed-8)(see [commit](https://github.com/RazrFalcon/resvg/commit/82d77a0b54535e3c3cc514848ef17409b0a4c2b5)).

Add a test to ensure it is now fixed.

```shell
thread '<unnamed>' panicked at 'the previous segment must be M/L/C'
thread 'main' panicked at 'the previous segment must be M/L/C', usvg/src/pathdata.rs:219:17

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Expand Down

1 comment on commit fa81b20

@vercel
Copy link

@vercel vercel bot commented on fa81b20 Nov 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

resvg-js – ./

resvg-js-git-main-yisibl.vercel.app
resvg-js-yisibl.vercel.app
resvg-js.vercel.app

Please sign in to comment.