File

util.jsonschema: Fix validation to not assume presence of "type" field MattJ reported a curious issue where validation did not work as expected. Primarily that the "type" field was expected to be mandatory, and thus leaving it out would result in no checks being performed. This was likely caused by misreading during initial development. Spent some time testing against https://github.com/json-schema-org/JSON-Schema-Test-Suite.git and discovered a multitude of issues, far too many to bother splitting into separate commits. More than half of them fail. Many because of features not implemented, which have been marked NYI. For example, some require deep comparisons e.g. when objects or arrays are present in enums fields. Some because of quirks with how Lua differs from JavaScript, e.g. no distinct array or object types. Tests involving fractional floating point numbers. We're definitely not going to follow references to remote resources. Or deal with UTF-16 sillyness. One test asserted that 1.0 is an integer, where Lua 5.3+ will disagree.

+
−Welcome hackers!
+
−
+
−This project accepts and *encourages* contributions. If you would like to get 
+
−involved you can join us on our mailing list and discussion rooms. More 
+
−information on these at https://prosody.im/discuss
+
−
+
−Patches are welcome, though before sending we would appreciate if you read 
+
−docs/coding_style.md for guidelines on how to format your code, and other tips.
+
−
+
−Documentation for developers can be found at https://prosody.im/doc/developers
+
−
+
−Have fun :)