-
- Downloads
`mermaid`: refactor config to use `mermaid_config.js` include, only require...
`mermaid`: refactor config to use `mermaid_config.js` include, only require `mermaid.version` in `_config.yml` (#909) This PR has a bit of scope creep! This PR now: - changes the mermaid opt-in logic to only check for the existence of a `mermaid` key instead of `mermaid != false`: this resolves the follow-up in #857 - changes the behaviour of mermaid configuration - instead of using `mermaid_init.html` with default settings, makes the include `mermaid_config.js` - the include is loaded directly into the contents of `mermaid_initialize` - by default, it is an empty object (i.e. `{}`), triggering the defaults - updates docs - adds an example to the markdown kitchen sink It does significantly change the interface provided in #857, and I apologize for the confusion. However, given the discussion in this PR, I think it's the best move forward!
Showing
- _config.yml 8 additions, 20 deletions_config.yml
- _includes/head.html 1 addition, 1 deletion_includes/head.html
- _includes/mermaid_config.js 1 addition, 0 deletions_includes/mermaid_config.js
- _includes/mermaid_init.html 0 additions, 58 deletions_includes/mermaid_init.html
- _layouts/default.html 6 additions, 2 deletions_layouts/default.html
- docs/configuration.md 7 additions, 17 deletionsdocs/configuration.md
- docs/index-test.md 14 additions, 1 deletiondocs/index-test.md
- docs/ui-components/code.md 29 additions, 2 deletionsdocs/ui-components/code.md
_includes/mermaid_config.js
0 → 100644
_includes/mermaid_init.html
deleted
100644 → 0
Please register or sign in to comment