rschmitt commented on issue #213: URL: https://github.com/apache/logging-log4j-transform/issues/213#issuecomment-3165719119
> I believe we already do emit warnings on unknown keys, but only for V1 configuration, where the list of properties is basically fixed. When converting from V2 configuration files, we don't really know all the properties especially for custom Log4j Core plugins. Interesting. All of this information is new to me. I mainly work in library development and build engineering, so I just call the logger API and let someone else worry about configuring it. > However in the particular case of `rootLogger` and `logger` the plugins are fixed, so I could add warnings for unknown properties. Sounds like a plan: 1. Strictly validate fields in fixed structures 👍 2. Preserve unknown fields in late-bound and extensible structures 👍 (you couldn't use an HTTP server that failed on "unknown headers") -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
