The migration guide for Meteor 2.12 mentions a way to enable warnings about an old API, so out of curiosity I enabled it on my project. It looks like every use of methods like remove, insert or findOne (and maybe others, too) on MongoDB collections trigger that warning. That's fine so far, because it informs me what will be removed in Meteor 3.
However, neither the warning nor the migration guide mention what API should be used instead. That makes the warning kind of pointless, because even if I am willing to migrate to a newer API, I do not have any idea what API that should be. So I checked the documentation on collections and it looks like insert etc. are still the way to use MongoDB collections. 🤔
So the question is: What should Meteor users use instead, any why does the documentation not contain a pointer to the new API? That would make migration easier.
The migration guide for Meteor 2.12 mentions a way to enable warnings about an old API, so out of curiosity I enabled it on my project. It looks like every use of methods like
remove,insertorfindOne(and maybe others, too) on MongoDB collections trigger that warning. That's fine so far, because it informs me what will be removed in Meteor 3.However, neither the warning nor the migration guide mention what API should be used instead. That makes the warning kind of pointless, because even if I am willing to migrate to a newer API, I do not have any idea what API that should be. So I checked the documentation on collections and it looks like
insertetc. are still the way to use MongoDB collections. 🤔So the question is: What should Meteor users use instead, any why does the documentation not contain a pointer to the new API? That would make migration easier.