-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
feat: JSON format representation of diagram is returned in render fun… #6095
base: develop
Are you sure you want to change the base?
Conversation
|
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
commit: |
@knsv @sidharthv96 @Yokozuna59 This pr is able to solve the problem of not being able to get the data structure of the layout information, but has not been able to get the merge, this problem has been bothering me for a long time, and I have been using the fork way of data conversion, is the team currently considering solving this problem, or is it because there is already a program being implemented? I would like to get a response to this question, thank you very much! |
@perseveringman there is already a different approach for unifying rendering data that's being implemented. This approach adds a new dependency, and does extra processing while rendering, without any benefit for the majority of the end users. I would suggest you to continue using the fork, until the new approach is implemented for all these diagrams. If you could share your usecase, we could see if we can tweak |
📑 Summary
Intention of this PR is to export json format representation of mermaid diagram.
This PR supports JSON format representation for following types of diagrams
Resolves
https://github.com/orgs/mermaid-js/discussions/6094