From a2a08925b3f855c883e55f39eecc78fe009f9485 Mon Sep 17 00:00:00 2001 From: Patrick Spek Date: Tue, 18 Jan 2022 15:53:18 +0100 Subject: Fix up broken admonitions --- content/posts/2020/2020-07-15-config-3.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'content/posts/2020/2020-07-15-config-3.0.md') diff --git a/content/posts/2020/2020-07-15-config-3.0.md b/content/posts/2020/2020-07-15-config-3.0.md index 67a64c4..2b77dae 100644 --- a/content/posts/2020/2020-07-15-config-3.0.md +++ b/content/posts/2020/2020-07-15-config-3.0.md @@ -83,7 +83,7 @@ my $config = Config.new({ `foo` has been made into the `Str` *type object*, rather than a `Str` *value*. This was technically allowed in previous `Config` versions, but it comes with actual significance in 3.0. -{{< / admonition_md >}} +{{< / admonition >}} Using `.new` instead of `.read` is a minor syntactic change, which saves 1 word per program. This isn't quite that big of a deal. However, the optional `name` @@ -150,7 +150,7 @@ environment variable, as per the `Log` module's interface. When set to `7` (for "debug"), it will print the configuration files that are being merged into your `Config` and which environment veriables are being used as well. -{{< admonition_md title="note" >}} +{{< admonition title="note" >}} A downside is that the application using `Config` for its configuration must also support `Log` to actually make the new logging work. Luckily, this is quite easy to set up, and there's example code for this in `Log`'s README. -- cgit v1.1