Improve granularity of $jsonSchema validation errors in the case of inversion

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, any $jsonSchema validator expression which features a negation will simply state that the child expression or the schema matched (ex. given expression {$nor: [{$jsonSchema: {}}]} or {$jsonSchema: {not: {}}} and the document {}, you will get "schema matched" in the first case and "child expression matched" the second case). This ticket tracks the work necessary to make inversion provide detailed errors.

      Note that this has a surprising amount of complexity, namely because of the semantics of various $jsonSchema keywords and the way that some keywords are translated into MatchExpression.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Mihai Andrei
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: