[SERVER-50355] Improve bison error messages for missing named arguments Created: 18/Aug/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
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' " Would be great to detect the expected token or special case this scenario. |