From 2a2377c34e4c46546b343d1e5f92cf6fe63e2b16 Mon Sep 17 00:00:00 2001 From: Kaitlin Mahar Date: Tue, 26 Oct 2021 17:10:19 -0400 Subject: [PATCH 1/3] docs(NODE-3650): Note that boolean options must now be specified as booleans in upgrade guide --- docs/CHANGES_4.0.0.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/CHANGES_4.0.0.md b/docs/CHANGES_4.0.0.md index 9d7de85478e..94c49ed42d1 100644 --- a/docs/CHANGES_4.0.0.md +++ b/docs/CHANGES_4.0.0.md @@ -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 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. From c1d5ccad515f2caee8ac319dbbf0b717059b764a Mon Sep 17 00:00:00 2001 From: Kaitlin Mahar Date: Tue, 26 Oct 2021 17:23:44 -0400 Subject: [PATCH 2/3] Update docs/CHANGES_4.0.0.md Co-authored-by: Daria Pardue --- docs/CHANGES_4.0.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CHANGES_4.0.0.md b/docs/CHANGES_4.0.0.md index 94c49ed42d1..84cd8284cbb 100644 --- a/docs/CHANGES_4.0.0.md +++ b/docs/CHANGES_4.0.0.md @@ -175,7 +175,7 @@ Users should use `authMechanismProperties.SERVICE_NAME` like so: - 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 longer the case; any option documented as being a boolean must be specified as a boolean value. +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 longer the case; any option documented as being a boolean must be specified as a boolean value. ### db.collection no longer accepts a callback From 7d7d0e2582f13ea609c423682a31285c85a98aed Mon Sep 17 00:00:00 2001 From: Kaitlin Mahar Date: Tue, 26 Oct 2021 17:25:26 -0400 Subject: [PATCH 3/3] Forgot a word --- docs/CHANGES_4.0.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CHANGES_4.0.0.md b/docs/CHANGES_4.0.0.md index 84cd8284cbb..9bf4991b4d9 100644 --- a/docs/CHANGES_4.0.0.md +++ b/docs/CHANGES_4.0.0.md @@ -175,7 +175,7 @@ Users should use `authMechanismProperties.SERVICE_NAME` like so: - 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 longer the case; any option documented as being a boolean must be specified as a boolean value. +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