Need "equals" and "not equals" functions

Issue #33 resolved
James Powell repo owner created an issue

The DIFF function doesn’t quite work as this, as it finds changes from one JSON to another but ignoring missing elements, so to do a “not equals” one needs to do the DIFF both ways.

An actual “not equals” would both be quicker, and clearer and less prone to error.

Comments (5)

  1. James Powell reporter

    DIFF function also needs better documentation, as it is confusing as to the asymmetry between the two inputs.

  2. James Powell reporter

    Removed the Error terminals, as we sometime threw error on invalid JSON, and sometimes not. Could add it back later.

    Improved Testing, and found cases where identical, non-valid JSON would be “Equivalent”. ALso, valid identical JSON with following “rest of string” could identify as not equivalent. Modified to properly get the next JSOn value in all cases.

  3. Log in to comment