Problem/Motivation
I'm slowly reviewing all the tickets related to the dblog module. After some time of lecture it become clear that there are some tickets that are under the dblog.module (or the old watchdog.module) component are actually a more generic problem related to the Log system.
Examples of this tickets are:
- #2703877: Logger tries to replace {users_field_data} with current user object
- #2068111: Consolidate similar but same logging channels
- #2287039: Decide if we still want to translate log channel names and make modifications accordingly
- #2617330: LogMessageParser::parseMessagePlaceholders() needs to switch bang placeholder to colon placeholder
Also we have dblog and syslog, two modules that implement logger. If a problem affects both module, what category should reporters choose?
Proposed resolution
Create a Logger (or Logging) component in MAINTAINERS.txt.
@fgm said in #2617330: LogMessageParser::parseMessagePlaceholders() needs to switch bang placeholder to colon placeholder:
Note: I put this in the dblog component because there's currently no logger subsystem defined in the issue queue, but there should probably be one (which I'd volunteer to maintain, BTW).
So maybe we already have a candidate to maintain it.