- Lines 481 - 498: `val` and `x` is defined twice (hoisting)
- Lines 973 - 975 and 980 - 982: `expectedRemoves` and `expectedAdds`
is defined on lines 952 and 955
- Line 497: `return` after `throw`
- Lines 523 - 527: `e` already defined in same function scope
(hoisting)
- Line 937: Missed semicolon
- Line 1095: Very confused about ES6 “default parameter” set via
colon, which probably will be interpreted as Object - Babel failed to
build on my end, regarding [this
docs](https://mongodb.github.io/node-mongodb-native/api-generated/cursor
.html#count) it should be a Boolean, so we set it to `false` by default
- Line 1120: no need to set variable to `undefined`
- Lines 1122, 1128, and 1133: Define `doc` above while due to function
scope and hoisting `doc` is already allocated inside `while` and `try`
Setting mongoOptions.server.auto_reconnect was removed by #7880 via commit
0ffb9ac824, though it seems the Server
options still respect autoReconnect, even in version 2.2 of the driver:
http://mongodb.github.io/node-mongodb-native/2.2/api/Server.html
That said, having inspected the code of the `mongodb` package, I do not
believe this change is really critical, since the default value for
autoReconnect appears to be true.
More importantly, I can't find any support in the code of the `mongodb`
npm package or its dependencies for the claim that setting
mongoOptions.server.reconnectTries to 0 is the same as making it infinite,
so this commit sets it to Infinity.
* Reconnect to mongo indefinitely.
A fix for https://github.com/meteor/meteor/issues/7822
It seems the driver now always autoReconnects, but only for 30s.
To get the old (sensible) behavior of endlessly reconnecting, we set `reconnectTries` to 0.
* Releasing an rc of mongo package
Setting mongoOptions.server.auto_reconnect was removed by #7880 via commit
0ffb9ac824, though it seems the Server
options still respect autoReconnect, even in version 2.2 of the driver:
http://mongodb.github.io/node-mongodb-native/2.2/api/Server.html
That said, having inspected the code of the `mongodb` package, I do not
believe this change is really critical, since the default value for
autoReconnect appears to be true.
More importantly, I can't find any support in the code of the `mongodb`
npm package or its dependencies for the claim that setting
mongoOptions.server.reconnectTries to 0 is the same as making it infinite,
so this commit sets it to Infinity.
* Reconnect to mongo indefinitely.
A fix for https://github.com/meteor/meteor/issues/7822
It seems the driver now always autoReconnects, but only for 30s.
To get the old (sensible) behavior of endlessly reconnecting, we set `reconnectTries` to 0.
* Releasing an rc of mongo package
