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
More recent versions of Mermaid (v10.6.0) enable one to create git commit graph diagrams. I love using mermaid diagrams in my markdown files and I'm delighted that StackEdit supports rendering of many of the mermaid diagrams that I have made. However, today, I went to look at the documentation for mermaid to determine how to best display a git commit tree, and lo and behold, they have a specific graph type for it: gitGraph. However, upon entering in a very small amount of syntax for rendering a git tree graph, no diagram is being rendered in SlackEdit. Apparently, GitHub doesn't support this diagram type either, but I would imagine that using an up-to-date version of Mermaid would resolve the issue—both for StackEdit and GitHub. 😉
I tried bumping the mermaid version locally on package.json, but I'm getting errors from node-pre-gyp when trying to install sqlite3. I don't even know why sqlite is being pulled as a dependency.
Unfortunately, I'll leave this feature request to someone else. I also wanted a newer mermaid version.
More recent versions of Mermaid (v10.6.0) enable one to create git commit graph diagrams. I love using mermaid diagrams in my markdown files and I'm delighted that StackEdit supports rendering of many of the mermaid diagrams that I have made. However, today, I went to look at the documentation for mermaid to determine how to best display a git commit tree, and lo and behold, they have a specific graph type for it:
gitGraph
. However, upon entering in a very small amount of syntax for rendering a git tree graph, no diagram is being rendered in SlackEdit. Apparently, GitHub doesn't support this diagram type either, but I would imagine that using an up-to-date version of Mermaid would resolve the issue—both for StackEdit and GitHub. 😉The text was updated successfully, but these errors were encountered: