Skip to content

docs(NODE-3650): Note that boolean options must now be specified as booleans in upgrade guide #3017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 27, 2021
Merged

docs(NODE-3650): Note that boolean options must now be specified as booleans in upgrade guide #3017

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2a2377c
docs(NODE-3650): Note that boolean options must now be specified as b…
kmahar Oct 26, 2021
c1d5cca
Update docs/CHANGES_4.0.0.md
kmahar Oct 26, 2021
7d7d0e2
Forgot a word
kmahar Oct 26, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/CHANGES_4.0.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,6 +174,9 @@ Users should use `authMechanismProperties.SERVICE_NAME` like so:
- In a URI query param: `?authMechanismProperties=SERVICE_NAME:alternateServiceName`
- Or as an option: `{ authMechanismProperties: { SERVICE_NAME: 'alternateServiceName' } }`

### Non-boolean types are no longer accepted for boolean options
Previously, the driver would accept values that could be coerced to booleans (e.g. `0` and `1`) for boolean options (for example, `UpdateOptions.upsert`). This is no longer the case; any option documented as being a boolean must be specified as a boolean value.

### db.collection no longer accepts a callback

The only option that required the use of the callback was strict mode.
Expand Down