[
https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15441158#comment-15441158
]
Mikael Ståldal commented on LOG4J2-1181:
----------------------------------------
Thanks for reviewing.
The TODOs are due to that there is no way to do the flow trace logging in
{{ExtendedLogger}} without ifEnabled check (as you can do with regular logging
using the {{logMessage}} method). I am not sure if we should try to do
something about it, or just ignore it.
I fixed the documentation, does it look better?
> Scala wrapper for Log4j 2 API
> -----------------------------
>
> Key: LOG4J2-1181
> URL: https://issues.apache.org/jira/browse/LOG4J2-1181
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Affects Versions: 2.4.1, 2.5, 2.6, 2.6.1, 2.6.2
> Reporter: Mikael Ståldal
> Assignee: Mikael Ståldal
>
> Scala wrapper for Log4j 2 API which makes use of Scala features like macros
> and string interpolation.
> Inspired from [Typesafe's Scala
> Logging|https://github.com/typesafehub/scala-logging] but should use Log4j 2
> directly and expose its features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
