discernParser is documented incorrectly

[aubergene]

I was expecting to be able to do this

var parser = io.discernParser('blah.csv')
parser('name,price\nApple,1513\nPear,300')

[mhkeller]

Ya that's a good catch. It's documented correctly as returning a function that takes a file path but this would make more sense to rename and then separately create functions that expose the parser.

[aubergene]

Yeah, I think it would be good, then it easy to use it in situations where you've read the file by some other mechanism already.

[aubergene]

Wait, it's actually correct, it does return a parser, and works exactly I wanted, so it's just documented incorrectly, hoorah!

[mhkeller]

Hooray!

[mhkeller]

FYI i think the usage of this function is a bit bonkers since it has these weird two optional arguments whether it's a file path or a delimiter. I was planning on refactoring it later on when times seem worthy of a breaking change. Something like a first argument as a string and on option options object with delimter: true if that string should be treated as a delimiter

io.discernParser(strToTest[,{delimier: true}])

Issue: #63

[mhkeller]

This is fixed via 2c4ec09

[mhkeller]

Published in 3.0.0