Use Case

As a node driver engineer,
I want investigate our public api in the driver to look for outdated or legacy methods,
So that so that we can consider removing them or deprecating them for the 5.0 release.

User Impact

unknown

Acceptance Criteria

• Check other tickets in Node V5 epic and make sure all items marked for removal are already deprecated
• Check the methods already marked as deprecated in the driver, call them out in the document to make sure we can discuss whether or not to remove them
• Look through our public api for any apis that are legacy and we could consider deprecating, removing or refactoring to ease the implementation.
  • Probably don't bother with the client/collection/db, these mainly have helpers.
  • some potential areas to look in
    • Cursors
    • Streams
    • bulk operations
    • gridfs
• For each method, consider the following questions
  • Is this functionality present in NodeJS / a util now?  (for example - are we manually writing the equivalent of a for-await loop?)
  • Should we remove the API, deprecate the API, or rewrite the internals to be more maintainable?
• Document any such methods in a place that the team can review.

Follow Up Requirements

• additional tickets to file, required releases, etc