reporter output cruft

[ctcpip]

I just upgraded from v2 to v3, and the browser log output is now in JSON.stringify() format, which for my purposes is far from ideal -- namely due to character escaping necessary of the log message.

I know I can create my own reporter, but I want 99% of what the default TAP reporter does and would really prefer not to duplicate all that code and then have to manually keep it up-to-date.

I have created a draft PR #1463 which adds a log_processor config to address this. I didn't want to do anything more extensive without consulting the project maintainer(s) on the best way to go about this, but this is working as expected. Thoughts?

Just add the config function to testem.js, for example:

  log_processor(log) {
    return log.text;
  },

[ctcpip]

@johanneswuerbach thoughts?

[johanneswuerbach]

Sorry, I missed this. Adding the function seems reasonable and the PR already looks like a good start, the only thing missing would be a test to ensure we don't regress. 👍

[ctcpip]

@johanneswuerbach the PR is ready to go! #1463