[
https://issues.apache.org/jira/browse/LOG4J2-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239767#comment-17239767
]
ASF subversion and git services commented on LOG4J2-2966:
---------------------------------------------------------
Commit f8a9a5a146dfd7aa0cadd09e51b4e9237470ab5b in logging-log4j2's branch
refs/heads/release-2.x from Volkan Yazıcı
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=f8a9a5a ]
LOG4J2-2966 Replace String.valueOf() usages with
ParameterizedMessage.deepToString().
> Investigate replacing String.valueOf() usages in JTL with
> ParameterizedMessage.deepToString()
> ---------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2966
> URL: https://issues.apache.org/jira/browse/LOG4J2-2966
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Carter Kozak
> Assignee: Volkan Yazici
> Priority: Major
> Labels: JsonTemplateLayout
> Fix For: 3.0.0, 2.14.1
>
>
> As shared by [~ckozak] in [a GitHub pull request
> conversation|https://github.com/apache/logging-log4j2/pull/441#discussion_r527706889]:
> {quote}... we might want to use something like
> `ParameterizedMessage.deepToString(value)` for better handling of standard
> types, and exception handling in the case `toString` throws.{quote}
> This story aims to investigate the possibility of replacing
> {{String.valueOf()}} usages in JTL with
> {{ParameterizedMessage.deepToString()}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
