Update readme to show that it takes js vars not json about jsv HOT 4 CLOSED

I found it to be reasonably clear, better to keep the readme concise:

env.validate({ a : 1 }, { type : 'object', properties : { a : { type : 'string' }} });

The term json seems valid but maybe debatable. Since JSON is a subset of javascript writing json directly in a source file is ok (although this is not strictly JSON). If the function handled an unparsed string then 'str' might be a better name since we can't know it is JSON until we parse it. Working with JSON as a string in javascript would be seriously limiting anyway, best to parse it as soon as you can.

from jsv.

Dylan - thanks for responding! Although I will debate you on json being valid. :) JSON is specifically a text format for data interchange that coincidentally is also valid javascript. I don't disagree with what you're saying about turning JSON into a actual data sooner rather than later, but I think even a single line like "Please note that input to validate() takes js data not JSON text."

Either way though, thanks for making the library. Was just talking with a buddy yesterday about JSON Schema and he was complaining the node library he was using was particularly full featured - we looked through JSV and everything he was lacking was to be found here. :)

from jsv.

A valid point, easy enough to put in a pull request if you're adamant. I assume that second paragraph was directed at Gary Court :-)

from jsv.

Thank you for the compliment. I'll add more clarification to the README next update.

from jsv.