Currently AnaLog can distinguish, format and highlight the syntax of XML documents being printed into the log. It seems a cool feature but XML doesn't get more popular these days especially when it comes to logging of inter-service communication where REST/JSON approach is the de-facto standard.
It is required to implement the same functionality (detection, formatting, pretty-printing) for the logged JSON documents as well.
Additionally, to keep the application structure clean, it makes sense to extract the above logic into a separate, manageable layer which would be implemented by XML and JSON handlers (possibly with other formats support in the future). Every layer should have a toggle switch in the settings to let the user decide if he/she wants to use in or not (say, for the sake of performance).
Currently AnaLog can distinguish, format and highlight the syntax of XML documents being printed into the log. It seems a cool feature but XML doesn't get more popular these days especially when it comes to logging of inter-service communication where REST/JSON approach is the de-facto standard.
It is required to implement the same functionality (detection, formatting, pretty-printing) for the logged JSON documents as well.
Additionally, to keep the application structure clean, it makes sense to extract the above logic into a separate, manageable layer which would be implemented by XML and JSON handlers (possibly with other formats support in the future). Every layer should have a toggle switch in the settings to let the user decide if he/she wants to use in or not (say, for the sake of performance).