If you have a custom JSON encoder, and you try to test your log messages, your tests will fail because the MemoryLogger code path always encodes with the plain-vanilla JSON encoder.
Given FileDestination supports a custom JSON encoder, this is a problem.
If you have a custom JSON encoder, and you try to test your log messages, your tests will fail because the
MemoryLogger
code path always encodes with the plain-vanilla JSON encoder.Given
FileDestination
supports a custom JSON encoder, this is a problem.