vy commented on issue #1841: URL: https://github.com/apache/logging-log4j2/issues/1841#issuecomment-1980335413
@luisrm1012, @RafaelGB, I have the impression that the request here is to address a YAML inconsistency in Log4j, whereas * users could have simply quoted the value to avoid any ambiguity * [Spring Boot's `Level` parsing](/spring-projects/spring-boot/blob/2c4fb5baaa5af931730b610ecfee2645586ba0f1/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/context/logging/LoggingApplicationListener.java#L390) could have addressed this * etc. Put another way, I can think of several ways to solve your problem, but fixing it in Log4j. We can also find several other examples where a 3rd party integration behaves unintuitively and we can again land a fix to Log4j to work around that. IMHO, Log4j is not the right place to fix this problem and I am not inclined to proceed with this feature. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
