Expose registerDiagram()
for non-lazyLoadedDiagrams
#3710
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📑 Summary
Exposes the
registerDiagram()
function publicly asmermaid.mermaidAPI.registerDiagram
so that users can add their own diagrams at bundle-time.This is instead of using the
lazyLoadedDiagrams
config setting.Resolves #3701
📏 Design Decisions
In order to get this working, I updated
@mermaid-js/mermaid-mindmap
so that you can now get both theid
anddetector
by runningimport("@mermaid-js/mermaid-mindmap")
.Example usage
Also, to make life slightly easier,
registerDiagram
no longer takes a callback. Instead, it checks whether the diagram contains aninjectUtils
function, and if it does, it uses that as the callback instead.📋 Tasks
Make sure you
develop
branchrelease_9.2.0_buggfixes
branch, in case we want to back-port this to v9.2.0 as well.