On Fri, Nov 15, 2013 at 11:29 AM, Daniel DeLeo < " target="_blank"> > wrote:
Finally, my own inclination is that it’s better to define these things in code. As a major sticking point, there’s no “proc” type in JSON (how could there be?), but that would give you the most sane path to implementing validations that the framework doesn’t support yet. For example, if the framework doesn’t support integer ranges, I can easily write a bit of code to check if a number is in a range (so it’s a valid port number, say). With static data, such a thing wouldn’t be possible.Not suggesting we use it, but JSON Schema does support things like ranges and other attributes, though it still doesn't let you use code: http://json-schema.org/latest/json-schema-validation.html#anchor12--
Nathan L Smith
Archive powered by MHonArc 2.6.16.