db.collectionNames throws when options is null #934

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

If options is defined but null it isn't set to an empty object and the call to options.namesOnly causes an error.

Probably not the best fix here, but it gets the job done. You could probably remove the check for args.length, but I wasn't sure if it would have other side effects to just coerce to bool, so I made the smaller fix.

db.collectionNames throws when options is null
If options is defined but null, it isn't set to an empty object and the call to options.namesOnly causes an error.

@christkv christkv closed this Apr 8, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment