summaryrefslogtreecommitdiff
path: root/content/posts/2020/2020-07-15-config-3.0.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/posts/2020/2020-07-15-config-3.0.md')
-rw-r--r--content/posts/2020/2020-07-15-config-3.0.md4
1 files changed, 2 insertions, 2 deletions
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.