Currently the MongoClient constructor throws and error when provided a connection string like the following where one or more options is provided an empty string.

mongodb://localhost:27017/?key0=&key1=someString

The spec expects that the options would be parsed to this option object:

{
  key0: '',
  key1: 'someString'
}

Also note that when parsing the connection string, the spec considers the key to include the first '='. i.e. this would not be valid according to the spec.

mongodb://localhost:27017/?key0&key1=someString

Use Case

As a... Driver Engineer
I want... the MongoClient constructor to warn about, but accept keys with no values from connection string options
So that... we will improve our spec compliance

User Impact

__ N/A 

Dependencies

• TBD based on answers to unknowns

Unknowns

• how would this change affect shell?

Acceptance Criteria

Implementation Requirements

• Remove logic that throws when encountering keys with empty string values from connection string
• Add logic to to emit a warning when encountering keys with empty string values

Testing Requirements

• Pull in spec tests that test for this behaviour

Documentation Requirements

• DOCSP ticket should be generated.

Follow Up Requirements

• N/A