Basic query operators not loaded by default for update operation. about mingo HOT 4 OPEN

Hi @vigan-abd, thanks for reporting this issue. So the behaviour is not "broken" per se but rather it is a side effect of how operator loading works in the library which is by design to support tree-shaking for web installations. All query operators used in the update expression should be explicitly loaded.

That said, it might be better to load the basic query operators directly in the update context as done here. This would make the basic query operators available.

You can add the snippet below to your imports to fix it.

const { OperatorType, useOperators } = require("mingo/core");
const queryOperators = require("mingo/operators/query");
const { updateObject } = require('mingo/updater')

useOperators(OperatorType.QUERY, queryOperators);

A simpler option is to just use the side effect module below which loads a few more unnecessary operators.

require("mingo/init/basic") // loads minimal operators (including "$in") required for most common use-cases.
const { updateObject } = require('mingo/updater')

// do stuff here.

Will keep this issue open for now while I ponder a better way to handle this.

from mingo.

Running your example with the operators loaded is a no-op. For an actual MongoDB database it seems to be disallowed with the error below. See example here https://mongoplayground.net/p/JRwrWHT6pN3.

fail to run update: write exception: write errors: [Cannot use the part (_id) of (comments._id) to traverse the element ({comments: [ { date: null, body: "been there", _id: "comment1" }, { _id: "comment2", date: null, body: "done that" } ]})]

from mingo.

sorry, it should have been like this

db.collection.update({},
{
  $pull: {
    comments: {
      _id: {
        $in: [
          "comment1"
        ]
      }
    }
  }
},
{
  "upsert": false
})

from mingo.

That works as expected.

from mingo.