DOCSP-27376: removed support for dot notation in find* (#491)

Co-authored-by: Jordan Smith <[email protected]>

Author: rustagir

source/fundamentals/typescript.txt

@@ -84,13 +84,17 @@ You can find a code snippet that shows how to specify a type for the ``FindCurso
 class in the
 :ref:`Find Multiple Documents Usage Example <node-driver-find-usage-example-code-snippet>`.
 
+.. _node-ts-type-safety:
+
 Type Safety and Dot Notation
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-If you specify a query or update with **dot notation**, the {+driver-short+}
-provides type safety if your query or update does not
-:ref:`reference a nested instance of a recursive type <node-driver-recursive-types-dot-notation>`.
-Dot notation is a syntax you can use to navigate nested JSON objects.
+Starting in version 5.0, by default, the {+driver-short+} does not provide type
+safety for operations that search on fields expressed in **dot notation**. Dot
+notation is a syntax you can use to navigate nested JSON objects. When
+you construct a filter to pass to a query, the driver will not raise a
+type error even if you specify an incorrectly typed value for a field expressed
+in dot notation.
 
 The following code snippet defines the ``ClassificationPet`` interface,
 which includes a ``classification`` field that enables you to specify the
@@ -104,22 +108,40 @@ genus and color of dogs and cats:
      classification: { genus: "Canis" | "Felis"; color: string };
    }
 
-The following code snippet correctly raises a type error when specifying
-the genus of an unsupported animal in a query:
+The driver does not raise a type error for the following code sample,
+even though the value of ``classification.color`` is a boolean
+instead of a string:
 
 .. code-block:: typescript
 
-   database
-     .collection<ClassificationPet>("<your collection>")
-     .find({ "classification.genus": "Sylvilagus" });
+   await collection.findOneAndDelete({ "classification.color": false })
+
+You can enable type-checking by constructing filters as ``StrictFilter`` or
+``StrictUpdateFilter`` types.
 
-The type error raised by the preceding code snippet is as follows:
+.. warning::
+   
+   The ``StrictFilter`` and ``StrictUpdateFilter`` types are experimental and
+   may show type errors in valid queries where there should be none.
 
-.. code-block:: none
+In the following code sample, the filter is assigned a
+``StrictFilter`` type. Given this filter type, the {+driver-short+}
+reports a type error because the value of ``classification.color`` is a
+boolean instead of a string.
+
+.. code-block:: typescript
 
-   No overload matches this call.
-   ...
-   Type '"Sylvilagus"' is not assignable to type 'Condition<"Canis" | "Felis">'.
+   const filterPredicate: StrictFilter<ClassificationPet> = { "classification.color": false };
+   await collection.findOneAndDelete(filterPredicate);
+
+The following example assigns a ``StrictUpdateFilter`` type to an update
+filter. The {+driver-short+} reports a type error because the value of
+``classification.color`` is a boolean instead of a string.
+
+.. code-block:: typescript
+   
+   const updateFilter: StrictUpdateFilter<ClassificationPet> = { $set: { "classification.color": false } }
+   await pets.updateOne({}, updateFilter);
 
 Referencing Keys that Incorporate Variables
 ```````````````````````````````````````````

source/whats-new.txt

@@ -41,14 +41,24 @@ What's New in 5.0
 
 New features of the 5.0 {+driver-short+} release include:
 
+- By default, the driver no longer checks types referenced in dot notation
+  unless the ``StrictFilter`` type annotation is explicitly
+  used. To learn more about this change, see the :ref:`Typescript fundamentals
+  page <node-ts-type-safety>`.
+  
+  .. note::
+
+     This change is for Typescript only, and does not affect queries or operations
+     at runtime.
+
 - Optional installation of ``@aws-sdk/credential-providers`` as a dependency.
 
   - The driver no longer includes AWS SDK modules by default. Use the
     following ``npm`` command to install the SDK:
 
     .. code-block:: bash
 
-       npm install --save @aws-sdk/credential-providers@3.186.0
+       npm install --save "@aws-sdk/credential-providers@^3.201.0"
 
     If you install the SDK, ``npm`` notifies you if the version of the SDK you
     installed is incompatible with the driver. Once you install the