-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Exponse mermaid options in config.toml #453
Comments
Is fixed in the fork |
maxatome
pushed a commit
to maxatome/hugo-theme-learn
that referenced
this issue
Jan 23, 2024
maxatome
pushed a commit
to maxatome/hugo-theme-learn
that referenced
this issue
Jan 23, 2024
maxatome
pushed a commit
to maxatome/hugo-theme-learn
that referenced
this issue
Jan 23, 2024
maxatome
pushed a commit
to maxatome/hugo-theme-learn
that referenced
this issue
Jan 23, 2024
maxatome
pushed a commit
to maxatome/hugo-theme-learn
that referenced
this issue
Jan 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mermaid configuration can be difficult for some users because of some options that are meant to be secure and therefore are only settable during
mermaid.initialize
.By exposing the whole mermaid config object to our
config.toml
our users would have all the freedom they may require.This solves issues #443 #435.
The text was updated successfully, but these errors were encountered: