[Bug]: Mongo aggregate command doesn't parse BSON pipelines properly (variation of #6582)

[nzidol]

Is there an existing issue for this?

• I have searched the existing issues

Description

Aggregate command parses the user input for pipelines and the example from #6582 now works correct. However when mixing the pipeline with some JavaScript parsing errors occur though the evaluated value shown is a correct pipeline.

The key issue seems to be that the ':' that separates the key/value pair cannot be inside the {{JavaScript}} element although evaluated value is exactly the same.

Steps To Reproduce

1. Create a Mongo query.
2. Set the command type to Aggregate and choose any collection
3. In the array of pipelines use a command along the following lines :
   [ {$sort :{ _id : 1 }}, { $project: { age : 1}}, {$count: "userCount"} ]
4. Run the query. It shows a document count.
5. Add a table to the page and update the query:
   [ { $sort :{ {{ Table1.sortOrder.column != "" ? '_id : 1' : '_id : -1 ' }} } }, { $project: { age : 1}}, { $count: "userCount"} ]
6. Inspect the evaluated value, it shows the identical code from step 3
7. Run the query, a parsing error is reported
8. Update query to:
   [ { $sort :{ _id : {{ Table1.sortOrder.order == "desc" ? '-1' : '1' }} } }, { $project: { age : 1}}, { $count: "userCount"} ]
9. Inspect the evaluated value, it shows the identical code from step 3
10. Run the query, it shows a document count.
11. Update query to: (note the ':' )
    [ { $sort :{ {{ Table1.sortOrder.column != "" ? '_id' : '_id' }} : {{ Table1.sortOrder.order == "desc" ? '-1' : '1' }} } }, { $project: { age : 1}}, { $count: "userCount"} ]
12. Inspect the evaluated value, it shows the identical code from step 3
13. Run the query, it shows a document count.
14. Update query to: (note the ':' )
    [ { $sort :{ {{ Table1.sortOrder.column != "" ? '_id:' : '_id:' }} {{ Table1.sortOrder.order == "desc" ? '-1' : '1' }} } }, { $project: { age : 1}}, { $count: "userCount"} ]
15. Inspect the evaluated value, it shows the identical code from step 3
16. Run the query, it shows a parsing error.

Public Sample App

No response

Version

Self Hosted 1.8.0

[rohan-arthur]

@nzidol thanks for reporting this bug and appreciate the detailed description. We will look into this.

[sribalajig]

@rohan-arthur