Currently there is logger_journal_formatter defined, which is used to format the message for journal handling. After some revisions I am not sure if this is proper approach, here I would like to discuss whether it should be a thing or rather it should be replaced by logger_journal_h that would handle "formatting".
Pros of handling it as a separate module
It makes logger_journal_h much simpler.
It suits more as a separate module, as in reality it is handling what is said.
More flexibility left for the user.
Cons of separate module
Incautious user can make all messages from logger_journal_h invalid, and as a result ignored by journal.
If there is no message field (for example reports without default callback) then the message will be empty and it can be counterintuitive for user (all data will be in metadata).
Currently there is
logger_journal_formatterdefined, which is used to format the message for journal handling. After some revisions I am not sure if this is proper approach, here I would like to discuss whether it should be a thing or rather it should be replaced bylogger_journal_hthat would handle "formatting".Pros of handling it as a separate module
logger_journal_hmuch simpler.Cons of separate module
logger_journal_hinvalid, and as a result ignored by journal.What are Your thoughts?