Skip to content

Write content format failures to log file #45

@GoogleCodeExporter

Description

@GoogleCodeExporter
Complementing issue 22, we'll write content format failures to the log file. 
The Json.NET upgrade in issue 44 will make these most helpful for json parsing 
failures (the new lib version gives better failure messages).

Original issue reported on code.google.com by stephen....@gmail.com on 23 Jul 2014 at 4:04

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions