46 added support for decoding JSONL files. One issue was found that when the "formatString" does not include a date pattern, the formatted message still include formatted dates.
Description
Do not format date if no date pattern is specified in configured format string.
Validation performed
Loaded Log Viewer with example jsonl file.
Screenshot showing the formatted messages with dates
In config debug form, configured decoderOptions/formatString with value [%process.thread.name] %log.level %message%n, which is the default with the date pattern %d{yyyy-MM-dd HH:mm:ss.SSS} removed from the beginning.
Applied the config. After the page was reloaded, observed that the formatted messages no longer includes dates.
Screenshot showing the formatted messages do not include dates because now no such is configured in decoderOptions/formatString
References
46 added support for decoding JSONL files. One issue was found that when the "formatString" does not include a date pattern, the formatted message still include formatted dates.
Description
Validation performed
decoderOptions/formatString
with value[%process.thread.name] %log.level %message%n
, which is the default with the date pattern%d{yyyy-MM-dd HH:mm:ss.SSS}
removed from the beginning.