findOneAndUpdate option "new" has different default value from MongoDB findAndModify

In Mongoose doc http://mongoosejs.com/docs/api.html#model_Model.findOneAndUpdate

new: bool - true to return the modified document rather than the original. defaults to true

In MongoDB doc http://docs.mongodb.org/manual/reference/method/db.collection.findAndModify/

new Boolean Optional. When true, returns the modified document rather than the original. The findAndModify() method ignores the new option for remove operations. The default is false.

The mongoose default value of options.new is true while MongoDB is false. This is really counter-intuitive.

Any reason for this API design?

[mnort9]

This change makes the api less expressive IMO and will likely trip up newcomers. I believe most people will expect ‘findOneAndUpdate’ to return the updated doc. I can understand the desire to mirror the MongoDB driver, but creating an expressive high level api should take precedence.

Our dev team recently upgraded mongoose and we’ve had to go back to add what seems to be a boilerplate condition ({new: true}) to all of our ‘findOneAndUpdate’ queries. This seems like a step backward.

I could be missing something, but what scenario would you not want the updated doc to be returned?

[dreadrocksean]

There are better ways to implement an optimistic query than this. It is very counter intuitive and time wasting for new comers.