Are you sure it's good idea to remove checks?

Actually, I think we should keep checks even if some inconsistent behaviour exists because checks' errors are useful for debugging.
In my use case, I'd like to expect that find/findOne(), find/findOne({}), find/findOne(null), find/findOne(undefined) works as well as MongoCollection.
How do you think adding the following code in find and findOne:

check selector, Match.Optional Match.OneOf Object, String, null
check options, Match.Optional Object

Meteor API document says that the type of selector is Mongo Selector, Object ID, or String. So I think we should accept only Object, String, null and undefined.

Adding the above code yields the following result.

I've added check statements in this PR.

Thank you for your comment.
I added a new commit and updated the comparison table #224 (comment)

@dr-dimitru If you want me to fix something, could you tell me it?

Please note that we cannot satisfy with both check and the complete consistency with Meteor's find and findOne.
Personally, I'd like to keep check and break little consistency, but I'd like to pass null or undefined to FilesCollection.find and FilesCollection.findOne as well as Meteor's ones in order to avoid null and undefined checks.

@exKAZUu everything looks good to me, working on the new release now.
Your PR will be merged

I see. Thanks!