Use Case

We currently don't validate repeated options, which have undefined behavior per the spec unless the option is a list. The spec says we should warn users when we are provided such repeated options, which we do not currently do. Since we prefer to throw errors in such situations, we should fix our validation to do the check for repeated non-list type options.

User Impact

• Breaking Change Existing repeated URI option entries will start throwing upon constructing a MongoClient

Dependencies

• None

Unknowns

• readPreferenceTags is the only repeated "list" option I'm aware of. Are there others?
  • There are no others

Acceptance Criteria

Implementation Requirements

• When the URI options have been parsed validate that the result does not have multiple entries for options that do not support multiple entries

Testing Requirements

• Unit test sample connection strings with repeated options

Documentation Requirements

• Release notes about the breakage

Follow Up Requirements

• None