http://hg.omfa.de/prosody-hg/ en-us spec/util_jsonschema_spec.lua revision history http://hg.omfa.de/prosody-hg/log/eabd38507c1d/spec/util_jsonschema_spec.lua
Schemas can be either a boolean or a table (object) but since it only
checked for truthiness, the case of `false` would be handled
incorrectly.

There seems to be no tests that cover `then` and `else` being `false`,
only a couple that check the `if` keyword.]]> Kim Alvefur <zash@zash.se> Sun, 30 Mar 2025 17:27:23 +0200 http://hg.omfa.de/prosody-hg/log/72d7830505f0/spec/util_jsonschema_spec.lua Kim Alvefur <zash@zash.se> Sat, 02 Dec 2023 21:45:38 +0100 http://hg.omfa.de/prosody-hg/log/8c762a30eae0/spec/util_jsonschema_spec.lua
A test case was added in the middle, so all these need to be reordered.]]> Kim Alvefur <zash@zash.se> Sat, 20 May 2023 15:44:55 +0200 http://hg.omfa.de/prosody-hg/log/0fbb2b3fd4c0/spec/util_jsonschema_spec.lua Kim Alvefur <zash@zash.se> Sun, 23 Apr 2023 10:42:07 +0200 http://hg.omfa.de/prosody-hg/log/5d3e8a226840/spec/util_jsonschema_spec.lua Kim Alvefur <zash@zash.se> Sun, 23 Apr 2023 10:26:43 +0200 http://hg.omfa.de/prosody-hg/log/962a746842a0/spec/util_jsonschema_spec.lua
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.]]> Kim Alvefur <zash@zash.se> Sat, 22 Apr 2023 12:45:58 +0200 http://hg.omfa.de/prosody-hg/log/acf8a2372764/spec/util_jsonschema_spec.lua Kim Alvefur <zash@zash.se> Sat, 22 Apr 2023 12:44:53 +0200 http://hg.omfa.de/prosody-hg/log/dee080c2441e/spec/util_jsonschema_spec.lua
If this object key exists then this schema must validate against the
current object. Seems useful.]]> Kim Alvefur <zash@zash.se> Sun, 26 Mar 2023 15:20:07 +0200 http://hg.omfa.de/prosody-hg/log/8592770be63a/spec/util_jsonschema_spec.lua
If this field exists, then these fields must also exist.]]> Kim Alvefur <zash@zash.se> Sun, 26 Mar 2023 15:19:14 +0200 http://hg.omfa.de/prosody-hg/log/05ec70a9f755/spec/util_jsonschema_spec.lua
Absolute references, weird fractions, unevaluatedProperties???]]> Kim Alvefur <zash@zash.se> Sat, 11 Mar 2023 12:12:49 +0100 http://hg.omfa.de/prosody-hg/log/297b4cfcc3d9/spec/util_jsonschema_spec.lua
These seem to be using absolute URI references, Not Yet Implemented]]> Kim Alvefur <zash@zash.se> Sat, 11 Mar 2023 12:01:17 +0100 http://hg.omfa.de/prosody-hg/log/7929c0ffbe14/spec/util_jsonschema_spec.lua
Also touching on how arrays are indistinguishable from tables in Lua]]> Kim Alvefur <zash@zash.se> Sun, 09 Oct 2022 15:24:30 +0200 http://hg.omfa.de/prosody-hg/log/edbc888b1e05/spec/util_jsonschema_spec.lua
Full-URI references are not implemented]]> Kim Alvefur <zash@zash.se> Sun, 09 Oct 2022 15:24:26 +0200 http://hg.omfa.de/prosody-hg/log/cd7da871ce10/spec/util_jsonschema_spec.lua
Piped trough `sort -g`]]> Kim Alvefur <zash@zash.se> Sun, 09 Oct 2022 14:58:07 +0200 http://hg.omfa.de/prosody-hg/log/ca6a43fe0231/spec/util_jsonschema_spec.lua
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.]]> Kim Alvefur <zash@zash.se> Fri, 08 Jul 2022 14:38:23 +0200