4 ms·

All the examples are for validating JSON, and the documentation repeatedly mentions JSON, but I can't tell if this project is usable with non-JSON serialization

All the examples are for validating JSON, and the documentation repeatedly mentions JSON, but I can't tell if this project is usable with non-JSON serialization formats. It never explicitly mentions that it is JSON-only.

sradman 6y ago
It looks like it is more about declarative data structure validation in various language runtimes. Some of the implementations [1] (the interpreted languages like Perl, PHP, Python, and Ruby) seem to use the language's natural literal notation instead of JSON (or JavaScript Object Literals). It seems to be missing the "step" constraint from HTML5 Form Validations and nullability constraints from SQL (though there is overlap with 'required'). [1] https://livr-spec.org/introduction/implementations.html https://livr-spec.org/introduction/implementations.html