Use Case

As a developer
I want to remove the legacy boolean options (‘1’ ‘yes’ ‘no’ etc.) from our connection string parsing
So that our options parsing is simpler and easier to work with.

User Impact

* __ Any users making use of our legacy boolean options will have to explicitly provide boolean values in connection string and MongoClient constructor

Dependencies

• This is a breaking change, so it needs to go out in v6 of the node driver.

Unknowns

Acceptance Criteria

Implementation Requirements

• When parsing boolean values from options in the connection string, only accept true/false as valid values.
  • Remove getBoolean helper and update relevant logic in setOption

Documentation Requirements

• Will mark this as needs documentation changes to alert users that only explicit booleans will be accepted
• Release notes and migration guide will mention this change

Follow Up Requirements

• additional tickets to file, required releases, etc