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
HtmlConfig parsing error are silently ignored and the default values are used. This makes it hard for users to troubleshoot typos in their book.toml.
I tried this book.toml:
[output.html]
default-theme = "navy"curly-quotes = "true"# should have been: curly-quotes = true
I expected to see this happen: mdBook displays a warning or error message when building if the configuration contains a syntax error, like [WARNING] (mdbook::book): Configuration value for 'output.html.curly-quotes' is invalid, expected a boolean but got string "true".
It applies the valid config nodes and sets the default-theme to navy, but uses the default value for curly-quotes.
Instead, this happened: The build succeeds without any warning, and ignores the valid config nodes under output.html. So the default-theme falls back to default.
HtmlConfig
parsing error are silently ignored and the default values are used. This makes it hard for users to troubleshoot typos in theirbook.toml
.I tried this
book.toml
:I expected to see this happen: mdBook displays a warning or error message when building if the configuration contains a syntax error, like
[WARNING] (mdbook::book): Configuration value for 'output.html.curly-quotes' is invalid, expected a boolean but got string "true".
It applies the valid config nodes and sets the
default-theme
tonavy
, but uses the default value forcurly-quotes
.Instead, this happened: The build succeeds without any warning, and ignores the valid config nodes under
output.html
. So thedefault-theme
falls back to default.Meta
mdBook version b4bb442
The text was updated successfully, but these errors were encountered: