use encoding of underlying levelup

[mvayngrib]

so you can do

var db = level('blah.db', { valueEncoding: 'json' })
var feed = changes(db)
feed.append({ hey: 'ho' })
feed.createReadStream()
  .on('data', console.log) 
// { change: 1, value: { hey: 'ho' } }

this would mean for binary, you'd have to explicitly specify level('path', { valueEncoding: 'binary' })

[mafintosh]

lets add an options argument to module.exports and do options.valueEncoding || db.options.valueEncoding || 'binary'

[mvayngrib]

can valueEncoding passed in to options be different from db.options.valueEncoding? Seems like that would cause problems

[mafintosh]

yea. db.options.valueEncoding is just a default value. utf-8, json, binary, anEncoderObject is always accepted

[mvayngrib]

right, so maybe db.options.valueEncoding || options.valueEncoding || 'binary' would be better

[vespakoen]

db.options.valueEncoding is always set to my knowledge (defaults to utf8) so that wouldn't work afaik