Home / GitHub Page

Mermaid stopped working in lastest version 1.0.140

#1

The code in the image did render alrright in the previous version of Joplin

#2

Mermaid support is currently disabled unfortunately and is under review.

#3

Now that you have added support for plugins, is it possible to add mermaid again? I kinda liked its functionality and with the new plugins option everyone could choose, whether he wants to activate it or not.

#4

I’ve been trying to add it, but ran into a few issues. I believe I have to create custom rules to make it work and add the js to the viewer. I’ll try to work on it on the weekend again.

#5

Note that while I’ll accept a PR for Mermaid, for now I won’t mention it to the doc or provide support for it (and I think support will be needed because it seems to be a bit buggy and it’s not clear if someone is still maintaining this lib).

#6

Good to know, but I am not even sure, if I get it working…

This is actually a very good point. I think it should be mentioned in the FAQ and the README.md that you cannot maintain any of the plugins, because they are not your code (upstream) and that they are provided as is.

#7

The issue is that although we can say we don’t maintain plugins, if they are buggy or cause problems in Joplin, it still looks that it is Joplin that doesn’t work properly. It basically gives the feeling of an unstable app.

So there’s a fine line here and Mermaid is a bit at the limit - a bit buggy but at the same time very popular. So I guess we can add it, and rather than not documenting it we’ll put a warning saying that integration is experimental, that we cannot support it, and certain things won’t work, etc.

#8

Sounds good.

#9

Ideally with a big, fat :warning: right where the plugin is turned on. (And make it off by default.)