• Type: Sub-task
    • Resolution: Fixed
    • Priority: Unknown
    • 6.6.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • None
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      There are a few locations in the code base where a MongoError is used as a MongoServerError. Since the type signature of MongoServerError is changing to require errorResponse (a property not found in MongoError), the Node driver needs to be more careful in its type checking. 

      Acceptance Criteria

      Implementation Requirements

      • Type check rather than type cast the two instances where MongoError is used instead of MongoServerError

      Testing Requirements

      • Ensure all existing tests pass

              Assignee:
              Aditi Khare (Inactive)
              Reporter:
              Aditi Khare (Inactive)
              Bailey Pearson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: