Improve bison error messages for missing named arguments

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When an argument to an operator is missing, the error message is slightly misleading. As an example, for input {pipeline: [{}]} we get the following error:

      "syntax error, unexpected end of object at element 'end object' "
      "within array at index 0 of input pipeline"

      Would be great to detect the expected token or special case this scenario.

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Nicholas Zolnierz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: