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
Database system (MySQL, PostgresQL, etc.) and version: MySQL 5.7.x
Issue
The config variable $mermaidgDefaultTheme is ignored, as is config.DefaultTheme.value from extension.json; Mermaid\Config::getDefaultTheme() always returns forest no matter what.
Well, it always returns forestunless you modify it to return something else like default or neutral, or hard-code the theme value at MermaidParserFunction.phpline 80.
Step-debugging through src/Config.php reveals that $this->globalConfig is basically empty (at line 21) when Mermaid\Config::getDefaultTheme() is invoked from within Mermaid\MermaidParserFunction::parse (at line 80).
I assume this was meant to contain something, maybe settings from the config section of extension.json, or variables configured in LocalSettings.php, but it's beyond my level of understanding at the present moment to exactly surmise what or why.
The text was updated successfully, but these errors were encountered:
Setup and configuration
Issue
The config variable
$mermaidgDefaultTheme
is ignored, as isconfig.DefaultTheme.value
fromextension.json
;Mermaid\Config::getDefaultTheme()
always returnsforest
no matter what.Well, it always returns
forest
unless you modify it to return something else likedefault
orneutral
, or hard-code the theme value atMermaidParserFunction.php
line 80.Steps to reproduce the observation:
INSTALL.md
$mermaidgDefaultTheme
to something other thanforest
, as per INSTALL.md#configurationAmplifying information
Step-debugging through
src/Config.php
reveals that$this->globalConfig
is basically empty (at line 21) whenMermaid\Config::getDefaultTheme()
is invoked from withinMermaid\MermaidParserFunction::parse
(at line 80).I assume this was meant to contain something, maybe settings from the
config
section ofextension.json
, or variables configured inLocalSettings.php
, but it's beyond my level of understanding at the present moment to exactly surmise what or why.The text was updated successfully, but these errors were encountered: