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
{{ message }}
Repository navigation
Commit 599bbe9
Browse filesBrowse the repository at this point in the historyBrowse files
fix(core): Resolve escape sequences in fmt / parameterize messages
`parameterize` built the message with `String.raw`, so an escape such as
`\n` or `` \` `` stayed as a backslash sequence in the log body or event
message, while the template attribute used the cooked strings. A string
with an invalid escape sequence (e.g. a Windows path) has no cooked
value, so its text dropped out of the template entirely.
Build both from the cooked strings, falling back to the raw string where
there is no cooked value.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
0 commit comments