feat(NODE-4243): drop collection checks ns not found #4742
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Description
Dropping collections will no longer fail when the namespace isn't found.
Summary of Changes
collection.drop()to return false if a ns is not found.Notes for Reviewers
The AC on the ticket said to only update behaviour in the unified runner, but I took this opportunity to pull it out everywhere.
What is the motivation for this change?
NODE-4243
Release Highlight
Dropping a Collection No Longer Throws When NS not Found
This will now return
falseinstead.Double check the following
npm run check:lint)type(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript