René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Make fuller use of Serilog","articleBody":"Serilog offers a rich template string interface for logging, but currently we have a single template and build strings for it.\r\n\r\n@SeeminglyScience suggested we should instead implement an `ITextFormatter` for the various things we want to log.\r\n\r\nIn the original Serilog migration I made the following choices:\r\n* Contain Serilog references in a single part of the code\r\n* Maintain the old log level system rather than Serilog's\r\n* Use the `ILogger` interface still\r\n\r\nSerilog has fairly rich functionality but because of the way its named-argument string templating works, I'm not sure it can be used indirectly.\r\n\r\nBut a good use of Serilog would probably involve us using it directly, with its log levels, and ideally using the log-level-named methods (`logger.Verbose`, `logger.Error`, etc.).\r\n\r\nWith this, we would probably want to use Serilog's `ILogger` rather than our own implementation.\r\n\r\nWe should also migrate the testing away from writing a text file and toward making test sink for Serilog.","author":{"url":"https://github.com/rjmholt","@type":"Person","name":"rjmholt"},"datePublished":"2018-06-07T17:16:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/680/PowerShellEditorServices/issues/680"}