data logging

[pq]

Follow-up from #19.

I opted to add data to the log call but we could add a logData call instead. I don't have a strong preference...

(Aside: It'll be interesting to see how much of a drag all of these closures are in practice.)

/cc @devoncarew

[devoncarew]

Hey - not a lot of opinions here, but:

• a dedicated logData call could be useful, esp. to indicate that we have a prescriptive way to write the data
• if we're very proscriptive of what kind of data we can log (Map<String, Object>?), I wonder if we need both LogDataCallback data and ToJsonEncodable toJsonEncodablecallbacks? The LogDataCallback could just return a Map, and we'd document that all the objects in it needed to be jsonable (or, string, maps, lists, and ints)?

[pq]

Thanks for the feedback!

I'll land this for now but add notes to #19 to capture your ideas. I'll take another pass after we've talked through some of the ideas from my conversation w/ the apptree folks.

[devoncarew]

Hey - I used this API to pass structured data back from my sample app, and to log http headers back for network traffic. 👍 it worked great

[pq]

Great to hear!