-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
classDiagram breaks on any edit #858
Comments
Could you provide a sample diagram that breaks? |
Hi @kitsu , |
Is there a fix for this issue? |
@knsv it renders fine the first time. just edit something and it would break with the error mentioned above. |
If the fix is what DanShai has merged recently, when will it be released to cdnjs/unpkg? |
The issue is fixed and I am planning a release the coming days, rc-9 |
Thanks !!
On Mon, Jun 24, 2019 at 10:13 AM Knut Sveidqvist ***@***.***> wrote:
The issue is fixed and I am planning a release the coming days, rc-9
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#858>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKJPFOJPBX6HCT7KMUITV3P4D6DHANCNFSM4HYBG2EA>
.
--
With regards,
Raja
|
The fix for this was included in release 8.1.0. I am closing this for now. Reopen if there still is a problem. |
I am using Mermaid via VSCode-Markdown-Preview-Enhanced, and I noticed today that my classDiagrams are broken. I figured it was their problem, but testing on the Mermaid Live Editor I have similar problems.
In the editor paste any simple class diagram (e.g. the ReadMe example) and it will probably render fine, but preform any edit and the graph becomes unrecoverable broken.
The most common error I'm getting is
TypeError: Cannot read property 'x' of undefined
, but in the Live Editor I'm also gettings.node(...) is undefined
.I'm pushing my coworkers to use Markdown for internal documentation, and the classDiagram has been really handy. I hope someone is maintaining it now (it was abandoned last time I checked).
The text was updated successfully, but these errors were encountered: