Should mongoose show an error/warning if trying to delete on non-existing properties?

I was deleting two models based on a given court, and noticed a discrepancy in the logs (one time ObjectId and one time string):

Mongoose: bookings.remove({ court: ObjectId("5764ceaed5b3e76b78c149e9") }) {}  
Mongoose: events.remove({ court: '5764ceaed5b3e76b78c149e9' }) {}  

After further investigation, I realised the difference between the two models is that for events the court properly doesn’t exist (it should have been courts). Should mongoose not throw an error/warning if we’re deleting on properties which are not defined on the model?

What is the expected behaviour if we do this?

[hasezoey]

with the current mongoose version it removes those paths from the query, which could result in unwanted (and silent) behavior:

// NodeJS: 18.7.0
// MongoDB: 5.0 (Docker)
// Typescript 4.7.4
import * as mongoose from 'mongoose'; // mongoose@6.5.2

const userSchema = new mongoose.Schema({ prop1: String });

const UserModel = mongoose.model('User', userSchema);

(async () => {
  await mongoose.connect(`mongodb://localhost:27017/`, {
    dbName: 'verifyMASTER',
  });

  mongoose.set('debug', true);

  // Mongoose: users.remove({}, {})
  // remove { acknowledged: true, deletedCount: 0 }
  console.log('remove', await UserModel.remove({ nonExistent: true }));
  // Mongoose: users.deleteOne({}, {})
  // deleteOne { acknowledged: true, deletedCount: 0 }
  console.log('deleteOne', await UserModel.deleteOne({ nonExistent: true }));
  // Mongoose: users.deleteMany({}, {})
  // deleteMany { acknowledged: true, deletedCount: 0 }
  console.log('deleteMany', await UserModel.deleteMany({ nonExistent: true }));

  await mongoose.disconnect();
})();

Note: the above code was run against a empty collection, that is why deletedCount is 0

Reproduction Repository / Branch: https://github.com/typegoose/typegoose-testing/tree/mongooseGh4251

this is probably related to strict being default now and strict removing unknown properties (though silently)

[vkarpov15]

By “do nothing with them” I meant they stay in the query as is and mongoose doesn’t cast them away,