Add JSON logging

[kevmoo]

No description provided.

[kevmoo]

@jcollins-g – I was pondering that this case might be nice to export everything to stdout – just so it's easy to pipe to a file or another process.

...let's discuss

[jcollins-g]

remove version number from CL; you don't know what version this will be published as.

[kevmoo]

So this is the pattern we've used through packages.

First change post-release: bump version & -dev

So 1.2.3 becomes 1.2.4-dev

The changelog entries follow:

## 1.2.4

Then if it becomes a breaking release...

1.2.4-dev become 2.0.0-dev

and update the changelog accordingly

That's how we (try) to manage all packages.

[jcollins-g]

ok, didn't know that was a standard practice as well. we'll try and do it that way then.

[devoncarew]

Not to muddy the waters, but I use ## unreleased as a placeholder.

[kevmoo]

done

[jcollins-g]

Request adding an end-to-end test of this feature that validates good JSON is written when generating docs for the test package.

[jcollins-g]

Writing this to stdout is OK if you can redirect stdout internally in dartdoc to something else when writing json, so an errant print statement somewhere doesn't break your JSON.

Indeed, that's how this should be implemented generally, assuming that's possible in dart. That way you don't have to require that all output goes through this library.

[kevmoo]

Request adding an end-to-end test of this feature that validates good JSON is written when generating docs for the test package.

On it!

[kevmoo]

@jcollins-g – PTAL

[jcollins-g]

This looks pretty good now. Use zones to redirect errant print statements as discussed and then this will be fine.

[kevmoo]

PTAL