From e3ab4e680bf28c40798ba79bad057fa01e45be9d Mon Sep 17 00:00:00 2001 From: Michael Dwyer Date: Tue, 31 Oct 2017 09:46:46 -0500 Subject: [PATCH] Fix typo All other documentation and code suggests that the replacement token is of the form `{var}` and not `%var%` --- doc/message-structure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/message-structure.md b/doc/message-structure.md index 093a10ca..63c6f19b 100644 --- a/doc/message-structure.md +++ b/doc/message-structure.md @@ -5,7 +5,7 @@ The table below describes which keys are always available for every log message. key | type | description -----------|---------------------------|------------------------------------------------------------------------------- -message | string | The log message. When the `PsrLogMessageProcessor` is used this string may contain placeholders that will be replaced by variables from the context, e.g., "User %username% logged in" with `['username' => 'John']` as context will be written as "User John logged in". +message | string | The log message. When the `PsrLogMessageProcessor` is used this string may contain placeholders that will be replaced by variables from the context, e.g., "User {username} logged in" with `['username' => 'John']` as context will be written as "User John logged in". level | int | Severity of the log message. See log levels described in [01-usage.md](01-usage.md). level_name | string | String representation of log level. context | array | Arbitrary data passed with the construction of the message. For example the username of the current user or their IP address.