prosody.git - unofficial mirror of the prosody mercurial project

	Commit message (Collapse)	Author	Age	Files	Lines
*	util.jsonschema: Return basic structured validation response	Kim Alvefur	2023-12-02	1	-0/+1
\|
*	util.jsonschema: Update test suite ignore rules	Kim Alvefur	2023-05-20	1	-5/+6
\| \| \| \|	A test case was added in the middle, so all these need to be reordered.
*	util.jsonschema: Fix UTF-8ness of 'minLength' and 'maxLength'	Kim Alvefur	2023-04-23	1	-2/+0
\|
*	util.jsonschema: Implement 'minContains' and 'maxContains'	Kim Alvefur	2023-04-23	1	-2/+0
\|
*	util.jsonschema: Tweak description of disabled test	Kim Alvefur	2023-04-22	1	-1/+1
\| \| \| \| \| \|	This doesn't fail because of additionalProperties, looks more like some issue with recursive definitions and util.jsonpointer that I don't want feel like investigating now.
*	util.jsonschema: Enable passing IEEE 754 equality test	Kim Alvefur	2023-04-22	1	-1/+0
\|
*	util.jsonschema: Implement 'dependentSchemas'	Kim Alvefur	2023-03-26	1	-1/+1
\| \| \| \| \|	If this object key exists then this schema must validate against the current object. Seems useful.
*	util.jsonschema: Implement 'dependentRequired'	Kim Alvefur	2023-03-26	1	-1/+0
\| \| \| \|	If this field exists, then these fields must also exist.
*	util.jsonschema: Disable some further new failing tests	Kim Alvefur	2023-03-11	1	-1/+4
\| \| \| \|	Absolute references, weird fractions, unevaluatedProperties???
*	util.jsonschema: Ignore some new tests in test suite	Kim Alvefur	2023-03-11	1	-1/+4
\| \| \| \|	These seem to be using absolute URI references, Not Yet Implemented
*	util.jsonschema: Ignore test case for JavaScript specific detail	Kim Alvefur	2022-10-09	1	-0/+1
\| \| \| \|	Also touching on how arrays are indistinguishable from tables in Lua
*	util.jsonschema: Ignore some further test cases for URI references	Kim Alvefur	2022-10-09	1	-0/+5
\| \| \| \|	Full-URI references are not implemented
*	util.jsonschema: Sort test cases to skip	Kim Alvefur	2022-10-09	1	-7/+7
\| \| \| \|	Piped trough `sort -g`
*	util.jsonschema: Fix validation to not assume presence of "type" field	Kim Alvefur	2022-07-08	1	-0/+102
	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.